Loading the registry…
Cursor Rules are .cursorrules / .cursor/rules files that steer Cursor's AI; scanned with the same pipeline.
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.
Cursor Rules are .cursorrules / .cursor/rules files that steer Cursor's AI. Review the scanned source before copying them into your own project.
nerlo install -- trash-sim
7 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.
v1.4.0
4 findings · 0.7s
v2.0.11
5 findings · 8.5s
v0.3.74
3 findings · 1.8s
v0.1.0
0 findings · 3.2s
v0.1.0
0 findings · 3.2s
v0.71.0
3 findings · 0.4s
v2.3.8
31 findings · 8.1s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 1.7s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 22, 2026 | Flagged62 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicabletrivy: completeosv-scanner: completetrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
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 46 findings across every scanner that examined this package.
These findings are in files this artifact installs and are not placeholder values. No false-positive basis can be corroborated for such a finding, so this review never dismisses one; they were not sent to the model and stand at their scanner's severity.
2 GHSA-28wg-ghj8-5hjv
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-2v37-7h3g-55p8
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-3v7f-55p6-f55p
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-4w7w-66w2-5vf9
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-6g55-p6wh-862q
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-c2c7-rcm5-vvqj
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-fx2h-pf6j-xcff
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-fxqj-rqcc-2cmp
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-mw96-cpmx-2vgc
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-p9ff-h696-f583
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-qx2v-qp2m-jg93
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-r28c-9q8g-f849
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-v2wj-q39q-566r
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 GHSA-v6wh-96g9-6wx3
Files: /repo/bun.lock, /repo/package-lock.json · reported by osv-scanner
2 hooks-no-pretooluse
Files: settings.local.json, .claude/settings.local.json · reported by agentshield
2 permissions-no-deny-list
Files: settings.local.json, .claude/settings.local.json · reported by agentshield
1 AAK-LEGAL-002
Files: package.json · reported by agent-audit-kit
1 AAK-TRUST-004
Files: .claude/settings.local.json · reported by agent-audit-kit
1 AAK-TRUST-006
Files: .claude/settings.local.json · reported by agent-audit-kit
1 CVE-2025-13465
Files: bun.lock · reported by trivy
1 CVE-2026-2950
Files: bun.lock · reported by trivy
1 CVE-2026-4800
Files: bun.lock · reported by trivy
1 EXCESSIVE_FILE_COUNT
Files: /repo/. · reported by cisco-skill-scanner
1 FILE_MAGIC_MISMATCH
Files: /repo/public/robots.txt · reported by cisco-skill-scanner
1 GHSA-4x5r-pxfx-6jf8
Files: /repo/bun.lock · reported by osv-scanner
1 GHSA-f23m-r3pf-42rh
Files: /repo/bun.lock · reported by osv-scanner
1 GHSA-r5fr-rjxr-66jc
Files: /repo/bun.lock · reported by osv-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
1 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md · reported by cisco-skill-scanner
Multiple high-severity vulnerabilities and permission concerns identified.
The artifact contains numerous high-severity vulnerabilities in its dependencies, as indicated by multiple GHSA and CVE findings in `bun.lock` and `package-lock.json`. These vulnerabilities could lead to various security compromises, including potential remote code execution or data exposure. Additionally, findings related to `permissions-no-deny-list` and `AAK-TRUST-004` in `settings.local.json` suggest potential issues with permission handling or sensitive configuration access. The `LOW_ANALYZABILITY` finding for the repository indicates challenges in fully assessing the code's security posture.
Concern level assessed by the review: High. This is the review's scale, not the registry badge.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.