io.github.sidinsearch/bugproof

MCPattested
v1.6.5io.github.sidinsearchUnknownUpdated 4mo 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…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

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.
4mo agoLast update
Package
Authorio.github.sidinsearch
LicenseUnknown
Version1.6.5
Sourcemcp-registry
npmbugproof
GitHubsidinsearch/BugProof
SBOMCycloneDX 1.6 ↓
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 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

18 tools · 1 privileged
Statically extracted from the published packagev1.6.5 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

captureNo description published

This tool published no description. Forge does not invent one.

replayNo description published

This tool published no description. Forge does not invent one.

inspectNo description published

This tool published no description. Forge does not invent one.

diffNo description published

This tool published no description. Forge does not invent one.

doctorNo description published

This tool published no description. Forge does not invent one.

shareNo description published

This tool published no description. Forge does not invent one.

pullNo description published

This tool published no description. Forge does not invent one.

watchNo description published

This tool published no description. Forge does not invent one.

listNo description published

This tool published no description. Forge does not invent one.

cleanNo description published

This tool published no description. Forge does not invent one.

capture-failureNo description published

This tool published no description. Forge does not invent one.

commandprivilegedNo description published

This tool published no description. Forge does not invent one.

nameNo description published

This tool published no description. Forge does not invent one.

replay-and-analyzeNo description published

This tool published no description. Forge does not invent one.

artifactNo description published

This tool published no description. Forge does not invent one.

compare-bugsNo description published

This tool published no description. Forge does not invent one.

leftNo description published

This tool published no description. Forge does not invent one.

rightNo description published

This tool published no description. Forge does not invent one.

0 of 18 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

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
Alternatives
Comparing tool surfaces…

Tools exposed

18 tools · 1 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.