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 -- firecrawl-style-guide
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 · 1.0s
v2.0.11
37 findings · 14.3s
v0.3.74
3 findings · 8.2s
v0.1.0
2 findings · 7.2s
v0.1.0
0 findings · 7.2s
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 · 2.2s
v0.71.0
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.6s
v2.3.8
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.5s
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.2s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 20, 2026 | Flagged67 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicabletrivy ·n/a: not applicableosv-scanner ·n/a: not applicabletrivy_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 42 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 23 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
The model could have called any of these a false positive and did not.
11 DATA_EXFIL_JS_NETWORK
Files: /repo/app/api/ai-analysis/route.ts, /repo/app/api/ai-readiness/route.ts, /repo/app/api/ai-readiness/test-sites.ts and 6 more · reported by cisco-skill-scanner
3 LOW_ANALYZABILITY
Files: /repo/components/ui, /repo/components/shared/effects, /repo · reported by cisco-skill-scanner
1 AAK-LEGAL-002
Files: package.json · reported by agent-audit-kit
1 AAK-SUPPLY-004
Files: package.json · reported by agent-audit-kit
1 EXCESSIVE_FILE_COUNT
Files: /repo/. · reported by cisco-skill-scanner
1 opt.nerlo-rules.nerlo-hardcoded-external-egress
Files: /repo/app/api/ai-analysis/route.ts · reported by nerlo-behavioral
1 opt.nerlo-rules.nerlo-js-secret-to-network-egress
Files: /repo/app/api/ai-analysis/route.ts · reported by nerlo-behavioral
23 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: AAK-SPLUNK-TOKLOG-001, SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: scripts/test-branding.mjs, /repo/SKILL.md, /repo/components/ui/SKILL.md and 9 more · reported by agent-audit-kit, cisco-skill-scanner
Potential for network egress and credential exposure
The artifact contains code with potential for network egress of sensitive information. A high-severity finding indicates JavaScript secrets could be sent over the network. Additionally, token logging is identified in `scripts/test-branding.mjs`, warranting attention.
Concern level assessed by the review: High. This is the review's scale, not the registry badge.
Showing 1 of 1; 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.