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 -- yasiruperera123/hack_25
4 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
Timed out
0 findings · 300.0s
v0.3.74
7 findings · 42.4s
v0.1.0
0 findings · 7.3s
v0.1.0
0 findings · 7.3s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.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 · 0.8s
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 22, 2026 | Scan Halted | — | agentshield ·n/a: not applicablecisco-skill-scanner ·!: timeoutagent-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 7 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.
3 AAK-OAUTH-001
Files: backend/src/routes/productRoutes.ts, backend/src/routes/authRoutes.ts, backend/src/routes/orderRoutes.ts · reported by agent-audit-kit
3 AAK-OAUTH-007
Files: backend/src/routes/productRoutes.ts, backend/src/routes/authRoutes.ts, backend/src/routes/orderRoutes.ts · reported by agent-audit-kit
1 AAK-LEGAL-002
Files: frontend/package.json · reported by agent-audit-kit
OAuth vulnerabilities detected in backend routes
The artifact contains multiple high-severity OAuth vulnerabilities in its backend routes, specifically in `authRoutes.ts`, `orderRoutes.ts`, and `productRoutes.ts`. These findings indicate potential issues with how the artifact handles authentication and authorization, which could lead to unauthorized access or privilege escalation. Further investigation is warranted to understand the full scope of these access control concerns.
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.