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 -- qtxbryan/atome-cs
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
26 findings · 10.4s
v0.3.74
1 finding · 3.5s
v0.1.0
0 findings · 4.8s
v0.1.0
0 findings · 4.8s
v0.71.0
38 findings · 0.3s
v2.3.8
38 findings · 9.1s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.3s
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.3s
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 21, 2026 | Flagged37 | — | 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 103 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.
15 DATA_EXFIL_JS_NETWORK
Files: /repo/client/src/api/chatApi.ts, /repo/client/src/api/configApi.ts, /repo/client/src/api/metaAgentApi.ts and 1 more · reported by cisco-skill-scanner
3 DATA_EXFIL_NETWORK_REQUESTS
Files: /repo/server/services/scraper_service.py · reported by cisco-skill-scanner
2 CVE-2026-40181
Files: client/package-lock.json · reported by trivy
2 GHSA-2j2x-hqr9-3h42
Files: /repo/client/package-lock.json · reported by osv-scanner
2 GHSA-jm82-fx9c-mx94
Files: /repo/server/requirements.txt, server/requirements.txt · reported by osv-scanner, trivy
2 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/server/data/SKILL.md · reported by cisco-skill-scanner
2 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/server/data/SKILL.md · reported by cisco-skill-scanner
1 AAK-LEGAL-002
Files: client/package.json · reported by agent-audit-kit
1 CVE-2026-28684
Files: server/requirements.txt · reported by trivy
1 CVE-2026-40260
Files: server/requirements.txt · reported by trivy
1 CVE-2026-40347
Files: server/requirements.txt · reported by trivy
1 CVE-2026-41168
Files: server/requirements.txt · reported by trivy
1 CVE-2026-41312
Files: server/requirements.txt · reported by trivy
1 CVE-2026-41313
Files: server/requirements.txt · reported by trivy
1 CVE-2026-41314
Files: server/requirements.txt · reported by trivy
1 CVE-2026-42561
Files: server/requirements.txt · reported by trivy
1 CVE-2026-48155
Files: server/requirements.txt · reported by trivy
1 CVE-2026-48156
Files: server/requirements.txt · reported by trivy
1 CVE-2026-48735
Files: server/requirements.txt · reported by trivy
1 CVE-2026-49460
Files: server/requirements.txt · reported by trivy
1 CVE-2026-49461
Files: server/requirements.txt · reported by trivy
1 CVE-2026-53537
Files: server/requirements.txt · reported by trivy
1 CVE-2026-53538
Files: server/requirements.txt · reported by trivy
1 CVE-2026-53539
Files: server/requirements.txt · reported by trivy
1 CVE-2026-53540
Files: server/requirements.txt · reported by trivy
1 CVE-2026-53571
Files: client/package-lock.json · reported by trivy
1 CVE-2026-53632
Files: client/package-lock.json · reported by trivy
1 CVE-2026-53666
Files: client/package-lock.json · reported by trivy
1 CVE-2026-53668
Files: client/package-lock.json · reported by trivy
1 CVE-2026-53669
Files: client/package-lock.json · reported by trivy
1 CVE-2026-54530
Files: server/requirements.txt · reported by trivy
1 CVE-2026-54531
Files: server/requirements.txt · reported by trivy
1 CVE-2026-54651
Files: server/requirements.txt · reported by trivy
1 CVE-2026-59935
Files: server/requirements.txt · reported by trivy
1 CVE-2026-59936
Files: server/requirements.txt · reported by trivy
1 CVE-2026-59937
Files: server/requirements.txt · reported by trivy
1 CVE-2026-59938
Files: server/requirements.txt · reported by trivy
1 CVE-2026-67213
Files: client/package-lock.json · reported by trivy
1 CVE-2026-67214
Files: client/package-lock.json · reported by trivy
1 CVE-2026-69153
Files: client/package-lock.json · reported by trivy
1 CVE-2026-71852
Files: server/requirements.txt · reported by trivy
1 CVE-2026-71870
Files: server/requirements.txt · reported by trivy
1 CVE-2026-73646
Files: client/package-lock.json · reported by trivy
1 FILE_MAGIC_MISMATCH
Files: /repo/server/requirements.txt · reported by cisco-skill-scanner
1 GHSA-28wg-ghj8-5hjv
Files: /repo/client/package-lock.json · reported by osv-scanner
1 GHSA-2v37-7h3g-55p8
Files: /repo/client/package-lock.json · reported by osv-scanner
1 GHSA-337j-9hxr-rhxg
Files: /repo/client/package-lock.json · reported by osv-scanner
1 GHSA-fx2h-pf6j-xcff
Files: /repo/client/package-lock.json · reported by osv-scanner
1 GHSA-fxqj-rqcc-2cmp
Files: /repo/client/package-lock.json · reported by osv-scanner
1 GHSA-jjmj-jmhj-qwj2
Files: /repo/client/package-lock.json · reported by osv-scanner
1 GHSA-r28c-9q8g-f849
Files: /repo/client/package-lock.json · reported by osv-scanner
1 GHSA-v6wh-96g9-6wx3
Files: /repo/client/package-lock.json · reported by osv-scanner
1 GHSA-wrjc-x8rr-h8h6
Files: /repo/client/package-lock.json · reported by osv-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
1 PYSEC-2026-2270
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3004
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3006
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3007
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3009
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3010
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3011
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3016
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3018
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3020
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3021
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3022
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3025
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3026
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3036
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3037
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3038
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3039
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3040
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3041
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3610
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3611
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3612
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3613
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3655
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3656
Files: /repo/server/requirements.txt · reported by osv-scanner
1 RESOURCE_ABUSE_INFINITE_LOOP
Files: /repo/server/services/bot_service.py · reported by cisco-skill-scanner
1 TOOL_ABUSE_UNDECLARED_NETWORK
Files: /repo/repo/README.md · reported by cisco-skill-scanner
High severity vulnerabilities and network egress capabilities detected.
The artifact contains multiple high severity vulnerabilities in its client and server dependencies, as indicated by CVEs and GHSA/PYSEC findings in `package-lock.json` and `requirements.txt`. It also exhibits network egress capabilities, with 18 instances of potential data exfiltration via network requests identified. A high severity resource abuse vulnerability, specifically an infinite loop, is present in `server/services/bot_service.py`.
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.