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 -- llm-assisted-project-template
5 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
0 findings · 0.6s
v2.0.11
21 findings · 7.0s
v0.3.74
1 finding · 1.2s
v0.1.0
0 findings · 2.9s
v0.1.0
0 findings · 2.9s
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 · 0.9s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 21, 2026 | Scan Halted | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicable | rejected |
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 22 findings across every scanner that examined this package.
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.
9 Test or fixture file — The match is in a test or fixture. Our own check confirmed the file is not part of what gets installed.
Rules: FILE_MAGIC_MISMATCH, SOCIAL_ENG_VAGUE_DESCRIPTION, HIDDEN_DATA_FILE and 2 more · Files: /repo/tests/setup/unit.setup.ts, /repo/tests/setup.ts, /repo/tests/__fixtures__/test-results/components-modal-component-89d68--a-semi-transparent-overlay-chromium/SKILL.md and 2 more · reported by cisco-skill-scanner
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.
3 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/playwright-report/data/SKILL.md, /repo/components/component-template/SKILL.md · reported by cisco-skill-scanner
3 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/playwright-report/data/SKILL.md, /repo/components/component-template/SKILL.md · reported by cisco-skill-scanner
2 LOW_ANALYZABILITY
Files: /repo/components/component-template, /repo · reported by cisco-skill-scanner
1 AAK-LEGAL-002
Files: package.json · reported by agent-audit-kit
1 BINARY_FILE_DETECTED
Files: /repo/bun.lockb · reported by cisco-skill-scanner
1 FILE_MAGIC_MISMATCH
Files: /repo/playwright.config.js · reported by cisco-skill-scanner
1 HIDDEN_DATA_FILE
Files:
Artifact contains highly unanalyzable code
The artifact includes code in `/repo/components/component-template` that exhibits low analyzability. This condition makes it challenging to fully determine the operational capabilities of this component. The inability to thoroughly analyze the code means potential risks, such as network egress, shell execution, credential access, or file writes, cannot be definitively ruled out.
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.
1 UNANALYZABLE_BINARY
Files: /repo/bun.lockb · reported by cisco-skill-scanner