@diffci.com/diffci

MCPcommunity
v0.2.4io.github.adityankale190895AGPL-3.0-onlyUpdated 1d agonpmGitHub

Observation-only CI/CD validation for AI coding agents.

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.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
2kDownloads/wk
1d agoLast update
Package
Authorio.github.adityankale190895
LicenseAGPL-3.0-only
Version0.2.4
Sourcenpm+mcp-registry
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
Dependencies✓ 21 resolved · none vulnerable
Tool surface3 tools · none privileged
Security scan✓ Cleanv0.2.4 · 1d agoHow well does this scan work?
CODE…ed/decode-data-html.jsVery large base64-looking blob in source (in minified file)
CODE…ed/decode-data-html.jsVery large base64-looking blob in source (in minified file)
EvalsNone
IndexedSep 22, 2026

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

Tools

3 tools · none privileged
Statically extracted from the published packagev0.2.4 · 1d 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.

diffci_checkAnalyze the repository, run inferred full and selected test commands when available, and report paired runtime. Sends nothing to DiffCI Cloud.

Analyze the repository, run inferred full and selected test commands when available, and report paired runtime. Sends nothing to DiffCI Cloud.

No input schema was published for this tool.

diffci_initSeed a repository with AI-agent instruction files for DiffCI.

Seed a repository with AI-agent instruction files for DiffCI.

No input schema was published for this tool.

diffci_verify_workflowCheck that a DiffCI GitHub Actions job cannot affect the rest of CI.

Check that a DiffCI GitHub Actions job cannot affect the rest of CI.

No input schema was published for this tool.

3 of 3 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

Observation-only CI/CD validation for AI coding agents.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-22 — observed resolution, not a publisher declaration.

21 packages resolved · 4 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

Declared but not resolved

1 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.