io.github.pdaxt/pqvault

MCPcommunity
v2.1.0io.github.pdaxtUnknownUpdated 7mo agoGitHub

Post-quantum secrets manager for AI agents. ML-KEM-768 + X25519 + AES-256-GCM.

source link failingno successful check on record
Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
7mo agoLast update
Package
Authorio.github.pdaxt
LicenseUnknown
Version2.1.0
Sourcemcp-registry
GitHubpdaxt/pqvault-rs
SBOMCycloneDX 1.6 ↓
Trust Status
D
30/100Risk
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
—Prompt-injection scan · findings+0/30
→ Publisher: remove instructions in the source aimed at AI clients rather than human readers
✓Obfuscation / exfil scan · 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⚠ Warnings (1)vHEAD · 3mo agoHow well does this scan work?
PROMPTdescriptionExfiltration-shaped instruction
EvalsNone
IndexedJun 13, 2026

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

Tools

Source not readable3mo ago

The repository archive could not be read at scan time (tarball fetch returned 404), so no tool declarations could be extracted from it. Nothing here is a statement about what this exposes.

About

Post-quantum secrets manager for AI agents. ML-KEM-768 + X25519 + AES-256-GCM.

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.