| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Patch: nothing that ships changed. The only commit since v0.24.2 is the switch back to trusted publishing (#309), and .github is not in the package's `files`. Cut to prove that switch. Nothing in the repository can check whether the trusted publisher is registered on npmjs.com — the registry does not expose it — and a dispatch run cannot reach the publish while 0.24.2 is the current version. A release is the only thing that exercises the OIDC exchange. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ThreatCrush Security Scan92 finding(s) HIGH/CRITICAL: 50 | MEDIUM: 42
…and 42 more. Full results in the Security tab. Snippets are redacted; ThreatCrush never prints matched credential material. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Summary
Patch: nothing that ships changed. The only commit since v0.24.2 is the switch back to trusted publishing (#309), and .github is not in the package's files list — the tarball is unchanged apart from the version field.
Why cut it
To prove that switch. Nothing in the repo can check whether the trusted publisher is registered on npmjs.com — the registry does not expose that config, which I checked — and a dispatch run cannot reach the publish step while 0.24.2 is the current version, because the skip guard stops first. A release is the only thing that exercises the OIDC exchange.
Two outcomes, both informative:
Verification
🤖 Generated with Claude Code