io.github.sidinsearch/bugproof

MCPattested
v1.6.5io.github.sidinsearchUnknownUpdated 2mo agonpmGitHub

Capture, replay, and debug failures with portable, executable bug artifacts

Executable bugs, not bug reports. Capture a failing command into a portable artifact that anyone can replay on their machine — same code, same env, same failure. Cryptographically signable. Cross-platform. Zero containers required. "Works on my machine" is not a bug report. Filing a backend or CLI bug today usually looks like this: A screenshot of a terminal A copy-pasted stack trace A list of…

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
2mo agoLast update
Package
Authorio.github.sidinsearch
LicenseUnknown
Version1.6.5
Sourcemcp-registry
npmbugproof
GitHubsidinsearch/BugProof
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 26cc53c
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface18 tools · 1 privileged
Security scan✓ Cleanv1.6.5 · 2mo ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Executable bugs, not bug reports. Capture a failing command into a portable artifact that anyone can replay on their machine — same code, same env, same failure. Cryptographically signable. Cross-platform. Zero containers required. "Works on my machine" is not a bug report. Filing a backend or CLI bug today usually looks like this: A screenshot of a terminal A copy-pasted stack trace A list of probably relevant files A best-guess description of how the reporter ran the thing Then the maintainer…

Keywords
mcp