Repository navigation
chore: archive legacy/taproot-assets-era to a tag, remove from main (63 Dependabot alerts) - #15
Merged
Conversation
…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).
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch had an error being deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Removes
legacy/taproot-assets-era/(179 files) frommainand preserves it at the annotated taglegacy/taproot-assets-era-final→ commitf8eebe3.legacy/README.mdkeeps 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.jsonfiles 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 onnext.Evidence it is dead
git grep -Il taproot-assets-era -- ':!legacy/'pnpm-workspace.yamlpackages/*only —pnpm -rnever enterslegacy/.github/workflows/ci.yml; runs only workspace scriptstools/check-boundaries.mjs:21SKIP_DIRSexplicitly contains'legacy'legacy/; repo root has no deploy pathpackage.jsonscripts (root +packages/sdk)legacyREADME.md:7,docs/ARCHITECTURE.md:269How verified
Node 22 + pnpm 10.28.2 (matching CI), after removal:
pnpm install --frozen-lockfile— cleanpnpm run verify— boundaries OK, typecheck clean, 170 tests passed / 3 skippedDiff touches nothing outside
legacy/(179 deletions + 1 modified README).Recovery