io.github.anthony-chaudhary/dos-kernel

MCPcommunity
v0.26.0io.github.anthony-chaudharyUnknownUpdated 2mo agoGitHub

Verify what agents actually shipped, arbitrate file collisions, refuse with structured reasons.

Catch your AI agents when they lie about what they shipped. The whole pitch in one recording: the agent claims two features shipped; git backs one. dos verify answers from the commits, the lie exits 1, and a gate on that exit code refuses the false "done". Every line is the real CLI's verbatim output — scripts/buildcaughtliecast.py re-records it whenever the output changes. Run a fleet of agents…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
2mo agoLast update
Package
Authorio.github.anthony-chaudhary
LicenseUnknown
Version0.26.0
Sourcemcp-registry
GitHubanthony-chaudhary/dos-kernel
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—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)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scan✓ Cleanv0.26.0 · 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

### Catch your AI agents when they lie about what they shipped. The whole pitch in one recording: the agent claims two features shipped; git backs one. dos verify answers from the commits, the lie exits 1, and a gate on that exit code refuses the false "done". Every line is the real CLI's verbatim output — scripts/buildcaughtliecast.py re-records it whenever the output changes. Run a fleet of agents on one repo. The left loop just feels like progress; the right one you can steer. The only…

Keywords
mcp