→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/10
→ 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>" }
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
—npm provenance (Sigstore)+0/5
→ Publish from GitHub Actions with the --provenance flag
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 0 resolved · none vulnerable
Tool surface40 tools · 1 privileged
Security scan✓ Cleanv1.7.0 · 12d ago
CODE…c/zeph/cascade-wasm.jsVery large base64-looking blob in source (in minified file)
CODE…zeph/cascade-wasm.d.tsVery large base64-looking blob in source (in minified file)
EvalsNone
IndexedJun 19, 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
Persistent project context for xAI Grok. IANA-registered .faf format.