proofseal
Regression memory for coding agents — seal how your repo behaves, then check over MCP (or in CI) that an edit didn't regress it: pass/drift/regressed/missing. With seal history, bisection, and staleness queries.
Description supplied by the publisher; it is a claim, not verified evidence.
- Name
- github:rudycelekli/proofseal
- Listed in
- GitHub
- Publisher
- @rudycelekli
- Published
- 2026-10-13
- License
- MIT
- Evidence
- Listed only, not analyzed yet
Source: https://github.com/rudycelekli/proofseal
What a full analysis of proofseal checks
Not checked yet. About 60 tools are analyzed every hour; each check links to its source when it runs:
- Publisher identity: not checked yet
- Repository ownership: not checked yet
- Organization verification: not checked yet
- Artifact provenance: not checked yet
- Source availability: not checked yet
- Version evidence: not checked yet
- Known vulnerabilities: not checked yet
- Install scripts: not checked yet
- Maintenance: not checked yet
- License: not checked yet
Before you install it
- Open the repository and confirm the account is the one you expect: look-alike names are common.
- Read what it asks for: files, accounts, network access and credentials it needs.
- Prefer a version from a verified publisher when one exists.