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 -- kadir49884/agore-token-creator
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.
v0.3.74
0 findings · 0.6s
v0.1.0
0 findings · 3.0s
v0.1.0
0 findings · 3.0s
v0.71.0
9 findings · 0.2s
v2.3.8
9 findings · 1.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
v2.0.11
No skill bundle was found in this artifact. What each scanner covers
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 · 0.9s
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 22, 2026 | Flagged63 | — | agentshield ·n/a: not applicablecisco-skill-scanner ·n/a: not applicableagent-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 18 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.
1 CVE-2024-1135
Files: requirements.txt · reported by trivy
1 CVE-2024-1681
Files: requirements.txt · reported by trivy
1 CVE-2024-6221
Files: requirements.txt · reported by trivy
1 CVE-2024-6827
Files: requirements.txt · reported by trivy
1 CVE-2024-6839
Files: requirements.txt · reported by trivy
1 CVE-2024-6844
Files: requirements.txt · reported by trivy
1 CVE-2024-6866
Files: requirements.txt · reported by trivy
1 CVE-2026-27205
Files: requirements.txt · reported by trivy
1 CVE-2026-28684
Files: requirements.txt · reported by trivy
1 PYSEC-2024-271
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2024-71
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1383
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1384
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1385
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1433
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1434
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2151
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2270
Files: /repo/requirements.txt · reported by osv-scanner
Multiple critical vulnerabilities in dependencies
The artifact includes dependencies with multiple high-severity vulnerabilities, as identified in `requirements.txt`. These vulnerabilities could potentially lead to various security risks, including remote code execution, denial of service, or information disclosure, depending on the specific component affected. Reviewing and updating these dependencies is strongly recommended before deployment.
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.