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 -- my-itinerary-app
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
Incomplete run
0 findings · 0.6s
v2.0.11
41 findings · 10.0s
v0.3.74
28 findings · 7.6s
v0.1.0
0 findings · 6.1s
v0.1.0
0 findings · 6.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.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 20, 2026 | Scan Halted | — | agentshield ·!: incompletecisco-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 69 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 62 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.
2 AAK-OAUTH-006
Files: src/app/auth/callback/google/page.tsx, src/app/auth/callback/facebook/page.tsx · reported by agent-audit-kit
2 AAK-SECRET-004
Files: src/lib/chat/storage.ts · reported by agent-audit-kit
2 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/.roo/rules/SKILL.md · reported by cisco-skill-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
40 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: AAK-MCP-003, AAK-SUPPLY-001, AAK-SECRET-007 and 5 more · Files: .cursor/mcp.json, /repo/src/app/itinerary/[id]/page.tsx, /repo/src/contexts/AuthContext.tsx and 15 more · reported by agent-audit-kit, cisco-skill-scanner
22 The review call did not complete.
Rules: FILE_MAGIC_MISMATCH, AAK-LEGAL-002, HIDDEN_DATA_FILE and 4 more · Files: /repo/MANUAL_INPUTS_NEEDED.txt, /repo/tasks/task_009.txt, /repo/tasks/task_003.txt and 19 more · reported by cisco-skill-scanner, agent-audit-kit
Critical findings in authentication and credential handling.
The artifact exhibits critical findings in authentication routes and social login components, indicating potential vulnerabilities in credential handling or authentication bypass. High severity findings also point to possible secret exposure within `src/lib/chat/storage.ts`. These issues warrant attention due to their potential impact on user data and system security.
Concern level assessed by the review: Critical. 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.
Showing 12 of 12; the rest are in the per-scanner reports above.