← Case index
Case file No.261 · pypi · stdio
verify-proof
io.github.csolomon0704-prog/verify-proof · v0.4.0
Verify timestamp proofs offline, anchor hashes through ProofLedger, keep agent run receipts.
Security score
93/100
Strong
Normalized over 100 points of available evidence.
Score breakdown
Known advisories
source: OSV.devNo advisories found in OSV for this package name. (Not proof of safety.)
Metadata change timeline
rug-pull detection- v0.3.4 → v0.4.0Oct 19, 2026
versionchanged version bump"0.3.4" → "0.4.0"
descriptionchanged description text edit"Verify blockchain timestamp proofs offline, or anchor a new one through ProofLedger." → "Verify timestamp proofs offline, anchor hashes through ProofLedger, keep agent run receipts."
packages.0.versionchanged package version bump"0.3.4" → "0.4.0"
- v0.3.3 → v0.3.4Oct 18, 2026
versionchanged version bump"0.3.3" → "0.3.4"
packages.0.versionchanged package version bump"0.3.3" → "0.3.4"
- First snapshot (v0.3.3)Oct 17, 2026
Tool lists: not published by the registry — unknown.
FAQ
auto-generated from the data aboveIs verify-proof safe?
MCPWatch gives verify-proof a heuristic security score of 93/100 (strong), based on 100 points of available evidence. This is an automated heuristic, not an audit.
Does verify-proof have known CVEs or vulnerabilities?
No advisories were found in OSV.dev for the pypi package verify-proof. That is not proof of safety.
When was verify-proof last updated?
The latest registry version is 0.4.0, published Oct 19, 2026. The last push to Fulcrum-Enterprises/verify-proof was on Oct 19, 2026. MCPWatch last checked it on Oct 20, 2026.
What license does verify-proof use?
GitHub reports the license of Fulcrum-Enterprises/verify-proof as MIT.