Skip to content

fix: correct dead GitHub repo URLs in demo + changelog#16

Open
dmchaledev wants to merge 1 commit into
mainfrom
claude/sleepy-rubin-4t8b4d
Open

fix: correct dead GitHub repo URLs in demo + changelog#16
dmchaledev wants to merge 1 commit into
mainfrom
claude/sleepy-rubin-4t8b4d

Conversation

@dmchaledev

Copy link
Copy Markdown
Contributor

Problem

Three links point at HailBytes/hailbytes-vulnerability-calculator — an erroneous hailbytes- prefix copy-pasted from the sibling packages. The actual repo, per package.json's repository.url, is HailBytes/vulnerability-calculator (no prefix), so all three currently 404:

File Link Where it surfaces
demo.html:139 footer "GitHub" link public-facing demo page
CHANGELOG.md:21 [Unreleased] compare link ships in the npm tarball (CHANGELOG.md is in package.json's files)
CHANGELOG.md:22 [0.1.0] release-tag link ships in the npm tarball

PR #12 noted the demo.html instance as out-of-scope and never fixed it; the two CHANGELOG.md links were missed entirely.

Fix

Drop the stray hailbytes- prefix so every link resolves to the real repository. Docs/markup only — no source, no calculation logic, no test changes.

Verification

$ rg hailbytes-vulnerability-calculator   # no matches remain
$ npm test
# tests 6
# pass 6
# fail 0

Fully self-contained (3-line diff across 2 files).

https://claude.ai/code/session_01Re7kJCLQCEgxHBfbqBJbBv


Generated by Claude Code

The repository slug carried an erroneous 'hailbytes-' prefix
(HailBytes/hailbytes-vulnerability-calculator), producing 404s. The
actual repo per package.json is HailBytes/vulnerability-calculator.

Fixes three broken links:
- demo.html footer 'GitHub' link (public-facing demo page)
- CHANGELOG.md [Unreleased] compare link
- CHANGELOG.md [0.1.0] release-tag link

CHANGELOG.md ships in the npm tarball, so these links also reached
package consumers.
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.

2 participants