We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
This artifact ships from 2 sources and their verdicts differ. The worst is github (Flagged). Installing from a cleaner source does not mean the others are safe — check the source you actually install from.
github: https://github.com/CongBao/failure-memory, 41 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- failure-memory
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
6 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v2.0.11
10 findings · 7.4s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 20, 2026 | Scan Halted | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·!: incompletenerlo-multi-source: complete | rejected |
Per-scanner history:
v0.3.74
6 findings · 1.7s
v0.1.0
0 findings · 3.6s
v0.1.0
4 findings · 3.6s
vv0.3.2
Incomplete run
0 findings · 1.8s
v0.1.0
0 findings · 11.0s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image.
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
Out of 20 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 9 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
Two keys had to turn. The model had to name a reason from a fixed list of six, and a deterministic check of ours — over which files this artifact actually installs — had to independently agree. Anything it could not corroborate is in “not reviewed” above, at full severity.
2 CI or editor configuration — The match is in build, CI or editor configuration, confirmed by our own check to be outside the installed artifact.
Rules: AAK-MARKETPLACE-004, AAK-MARKETPLACE-001 · Files: .github/plugin/marketplace.json · reported by agent-audit-kit
The model could have called any of these a false positive and did not.
4 HIDDEN_DATA_FILE
Files: /repo/.plugin/plugin.json, /repo/.cursor-plugin/plugin.json, /repo/.agents/plugins/marketplace.json and 1 more · reported by cisco-skill-scanner
2 AAK-MARKETPLACE-001
Files: .claude-plugin/marketplace.json, .agents/plugins/marketplace.json · reported by agent-audit-kit
2 AAK-MARKETPLACE-004
Files: .claude-plugin/marketplace.json, .agents/plugins/marketplace.json · reported by agent-audit-kit
1 opt.nerlo-rules.nerlo-install-run-bundled-artifact
Files: /repo/scripts/install.ps1 · reported by nerlo-install-instruction
9 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: opt.nerlo-rules.nerlo-install-fetch-raw-then-run, opt.nerlo-rules.nerlo-install-pipe-to-shell, PIPELINE_TAINT_FLOW and 2 more · Files: /repo/README.md, /repo/SKILL.md, /repo/skills/record-agent-failure/SKILL.md and 1 more · reported by nerlo-install-instruction, cisco-skill-scanner
Critical findings indicate potential for shell execution and data access.
The artifact's installation process includes instructions to pipe raw content to a shell and fetch raw content for execution, indicating potential for arbitrary command execution. Critical findings also highlight capabilities for sensitive data handling, file system writes, and database operations within core components like `install.go`, `index.go`, and `backup.go`. Additionally, high severity findings in `marketplace.json` files suggest potential vulnerabilities in external plugin definitions.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Showing 4 of 4; the rest are in the per-scanner reports above.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.