Skip to content

chore: archive legacy/taproot-assets-era to a tag, remove from main (63 Dependabot alerts) - #15

Merged
BitmapAsset merged 1 commit into
mainfrom
chore/archive-taproot-assets-era-legacy
Sep 3, 2026
Merged

BitmapAsset merged 1 commit into
mainfrom
chore/archive-taproot-assets-era-legacy

Conversation

@BitmapAsset

Copy link
Copy Markdown
Owner

What

Removes legacy/taproot-assets-era/ (179 files) from main and preserves it at the annotated tag legacy/taproot-assets-era-final → commit f8eebe3.

legacy/README.md keeps its full historical write-up (what the hub model was, why it was superseded) and gains a recovery pointer at the top. legacy/ci/ci-cd.yml — the parked, non-running old workflow — is retained.

Why

The prototype's three checked-in package-lock.json files were generating 63 of the repo's 64 Dependabot alerts: 1 critical (next), 25 high, 30 moderate, 7 low. Frontend 41, backend 20, sdk 2. None of it ships. That volume buried the one alert that mattered on the live tree (nanoid, #70, handled in #14).

Deleting the directory retires all 63 at the source. The alternative — dismissing 63 alerts as not_used — leaves the vulnerable code checked out and has to be redone every time a new CVE lands on next.

Evidence it is dead

Check Result
git grep -Il taproot-assets-era -- ':!legacy/' no hits
pnpm-workspace.yaml packages/* only — pnpm -r never enters legacy/
.github/workflows/ one file, ci.yml; runs only workspace scripts
tools/check-boundaries.mjs:21 SKIP_DIRS explicitly contains 'legacy'
Dockerfiles / compose / k8s / deploy scripts all 9 live inside legacy/; repo root has no deploy path
package.json scripts (root + packages/sdk) none reference legacy
README.md:7, docs/ARCHITECTURE.md:269 already document it as archived and not maintained

How verified

Node 22 + pnpm 10.28.2 (matching CI), after removal:

  • pnpm install --frozen-lockfile — clean
  • pnpm run verify — boundaries OK, typecheck clean, 170 tests passed / 3 skipped

Diff touches nothing outside legacy/ (179 deletions + 1 modified README).

Recovery

git checkout legacy/taproot-assets-era-final -- legacy/taproot-assets-era

…main

The pre-RuneBolt Taproot-Assets prototype (Next.js frontend, Node backend,
SDK, Docker/k8s deploy scripts) carried three checked-in package-lock.json
files that generated 63 Dependabot alerts (1 critical, 25 high, 30 moderate,
7 low) on a codebase that ships nowhere. That noise buried the one real alert
on the live tree.

Verified dead before removal:
  - git grep taproot-assets-era -- ':!legacy/'  -> no hits
  - pnpm-workspace.yaml is 'packages/*' only    -> pnpm -r never enters legacy/
  - .github/workflows/ci.yml is the only workflow and runs only workspace scripts
  - tools/check-boundaries.mjs explicitly skips 'legacy'
  - every Dockerfile/compose/k8s/deploy script in the repo lives INSIDE legacy/
  - README.md and docs/ARCHITECTURE.md already document it as not maintained

Preserved at annotated tag legacy/taproot-assets-era-final (f8eebe3).
Recover with:
  git checkout legacy/taproot-assets-era-final -- legacy/taproot-assets-era

legacy/README.md keeps its full historical write-up and gains the tag pointer.
legacy/ci/ci-cd.yml (parked, non-running) is retained.

Verified after removal: pnpm install --frozen-lockfile, pnpm run verify
(boundaries OK, typecheck clean, 170 tests passed / 3 skipped).
@vercel

vercel Bot commented Sep 3, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
runebolt Error Error Sep 3, 2026 10:00am UTC

Request Review

@BitmapAsset
BitmapAsset merged commit 4bfd0b3 into main Sep 3, 2026
2 of 3 checks passed
@BitmapAsset
BitmapAsset deleted the chore/archive-taproot-assets-era-legacy branch September 3, 2026 10:03

This branch had an error being deployed

1 failed deployment
Preview — 2b87df9e Deployed Sep 3, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant