Loading the registry…
Add your description here
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 -- pathatlas
6 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
4 findings · 7.8s
v0.3.74
0 findings · 1.2s
v0.1.0
1 finding · 4.0s
v0.1.0
0 findings · 4.0s
v0.71.0
25 findings · 0.4s
v2.3.8
24 findings · 1.5s
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 · 2.1s
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 20, 2026 | Flagged43 | — | agentshield ·n/a: not applicablecisco-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 54 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 3 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 GHSA-pw6j-qg29-8w7f
Files: /repo/uv.lock, uv.lock · reported by osv-scanner, trivy
1 CVE-2024-47081
Files: uv.lock · reported by trivy
1 CVE-2025-30167
Files: uv.lock · reported by trivy
1 CVE-2025-4565
Files: uv.lock · reported by trivy
1 CVE-2025-47287
Files: uv.lock · reported by trivy
1 CVE-2025-50181
Files: uv.lock · reported by trivy
1 CVE-2025-50182
Files: uv.lock · reported by trivy
1 CVE-2025-66418
Files: uv.lock · reported by trivy
1 CVE-2025-66471
Files: uv.lock · reported by trivy
1 CVE-2025-67724
Files: uv.lock · reported by trivy
1 CVE-2025-67725
Files: uv.lock · reported by trivy
1 CVE-2025-67726
Files: uv.lock · reported by trivy
1 CVE-2026-0994
Files: uv.lock · reported by trivy
1 CVE-2026-21441
Files: uv.lock · reported by trivy
1 CVE-2026-25645
Files: uv.lock · reported by trivy
1 CVE-2026-28684
Files: uv.lock · reported by trivy
1 CVE-2026-31958
Files: uv.lock · reported by trivy
1 CVE-2026-35536
Files: uv.lock · reported by trivy
1 CVE-2026-44431
Files: uv.lock · reported by trivy
1 CVE-2026-4539
Files: uv.lock · reported by trivy
1 CVE-2026-45409
Files: uv.lock · reported by trivy
1 CVE-2026-49853
Files: uv.lock · reported by trivy
1 CVE-2026-49854
Files: uv.lock · reported by trivy
1 CVE-2026-49855
Files: uv.lock · reported by trivy
1 DATA_EXFIL_NETWORK_REQUESTS
Files: /repo/backend/utils/job_search.py · reported by cisco-skill-scanner
1 GHSA-78cv-mqj4-43f7
Files: uv.lock · reported by trivy
1 opt.nerlo-rules.nerlo-py-secret-to-network-egress
Files: /repo/backend/utils/job_search.py · reported by nerlo-behavioral
1 PYSEC-2025-265
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-266
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-267
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-140
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-141
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1477
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1805
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1806
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1872
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1974
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1994
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1996
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1997
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1998
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1999
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-215
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2270
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2275
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2287
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2987
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3387
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3388
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3389
Files: /repo/uv.lock · reported by osv-scanner
3 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: TOOL_ABUSE_UNDECLARED_NETWORK, SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: /repo/repo/README.md, /repo/SKILL.md · reported by cisco-skill-scanner
Credential-to-network egress and high-severity vulnerabilities found.
The artifact's installed code performs network egress after accessing secrets in `/repo/backend/utils/job_search.py`. This capability could expose sensitive information to external systems. Additionally, the artifact includes dependencies with 29 high-severity vulnerabilities, which could lead to further compromise or unexpected behavior.
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 25 of 29; the rest are in the per-scanner reports above.