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.
6 critical findings reported by trivy, osv-scanner. The composite score alone does not reflect this — read the per-scanner reports below.
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 -- njs-mywork-bot
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
11 findings · 8.3s
v0.3.74
2 findings · 1.9s
v0.1.0
2 findings · 3.6s
v0.1.0
0 findings · 3.6s
v0.71.0
75 findings · 0.3s
v2.3.8
76 findings · 1.6s
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.4s
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 | Flagged36 | — | 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 166 findings across every scanner that examined this package. None of the 6 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 6 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
Two keys had to turn. The model had to name a reason from a fixed list of six, and a deterministic check of ours — over which files this artifact actually installs — had to independently agree. Anything it could not corroborate is in “not reviewed” above, at full severity.
4 Test or fixture file — The match is in a test or fixture. Our own check confirmed the file is not part of what gets installed.
Rules: SECRET_PASSWORD_VAR · Files: /repo/tests/test_config.py · reported by cisco-skill-scanner
The model could have called any of these a false positive and did not.
2 CVE-2026-45134
Files: uv.lock · reported by trivy
2 GHSA-f4xh-w4cj-qxq8
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
2 opt.nerlo-rules.nerlo-py-secret-to-network-egress
Files: /repo/src/bot/commands/put.py, /repo/src/bot/tools/work_tools/file_receiver.py · reported by nerlo-behavioral
2 RESOURCE_ABUSE_INFINITE_LOOP
Files: /repo/src/bot/filesystem_health.py, /repo/src/bot/slack_bot_mail_app.py · reported by cisco-skill-scanner
1 AAK-LANGCHAIN-SSRF-REDIR-001
Files: uv.lock · reported by agent-audit-kit
1 AAK-TASKS-003
Files: src/bot/slack_bot_task_app.py · reported by agent-audit-kit
1 CVE-2024-47081
Files: uv.lock · reported by trivy
1 CVE-2025-43859
Files: uv.lock · reported by trivy
1 CVE-2025-4565
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-53643
Files: uv.lock · reported by trivy
1 CVE-2025-64439
Files: uv.lock · reported by trivy
1 CVE-2025-65106
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-67221
Files: uv.lock · reported by trivy
1 CVE-2025-68480
Files: uv.lock · reported by trivy
1 CVE-2025-68664
Files: uv.lock · reported by trivy
1 CVE-2025-69223
Files: uv.lock · reported by trivy
1 CVE-2025-69224
Files: uv.lock · reported by trivy
1 CVE-2025-69225
Files: uv.lock · reported by trivy
1 CVE-2025-69226
Files: uv.lock · reported by trivy
1 CVE-2025-69227
Files: uv.lock · reported by trivy
1 CVE-2025-69228
Files: uv.lock · reported by trivy
1 CVE-2025-69229
Files: uv.lock · reported by trivy
1 CVE-2025-69230
Files: uv.lock · reported by trivy
1 CVE-2025-6984
Files: uv.lock · reported by trivy
1 CVE-2025-6985
Files: uv.lock · reported by trivy
1 CVE-2025-71176
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-22815
Files: uv.lock · reported by trivy
1 CVE-2026-23490
Files: uv.lock · reported by trivy
1 CVE-2026-25645
Files: uv.lock · reported by trivy
1 CVE-2026-26013
Files: uv.lock · reported by trivy
1 CVE-2026-27794
Files: uv.lock · reported by trivy
1 CVE-2026-28277
Files: uv.lock · reported by trivy
1 CVE-2026-28684
Files: uv.lock · reported by trivy
1 CVE-2026-30922
Files: uv.lock · reported by trivy
1 CVE-2026-34070
Files: uv.lock · reported by trivy
1 CVE-2026-34513
Files: uv.lock · reported by trivy
1 CVE-2026-34514
Files: uv.lock · reported by trivy
1 CVE-2026-34515
Files: uv.lock · reported by trivy
1 CVE-2026-34516
Files: uv.lock · reported by trivy
1 CVE-2026-34517
Files: uv.lock · reported by trivy
1 CVE-2026-34518
Files: uv.lock · reported by trivy
1 CVE-2026-34519
Files: uv.lock · reported by trivy
1 CVE-2026-34520
Files: uv.lock · reported by trivy
1 CVE-2026-34525
Files: uv.lock · reported by trivy
1 CVE-2026-34993
Files: uv.lock · reported by trivy
1 CVE-2026-40087
Files: uv.lock · reported by trivy
1 CVE-2026-41182
Files: uv.lock · reported by trivy
1 CVE-2026-41481
Files: uv.lock · reported by trivy
1 CVE-2026-44431
Files: uv.lock · reported by trivy
1 CVE-2026-44843
Files: uv.lock · reported by trivy
1 CVE-2026-45409
Files: uv.lock · reported by trivy
1 CVE-2026-47265
Files: uv.lock · reported by trivy
1 CVE-2026-48775
Files: uv.lock · reported by trivy
1 CVE-2026-48776
Files: uv.lock · reported by trivy
1 CVE-2026-50269
Files: uv.lock · reported by trivy
1 CVE-2026-54273
Files: uv.lock · reported by trivy
1 CVE-2026-54274
Files: uv.lock · reported by trivy
1 CVE-2026-54275
Files: uv.lock · reported by trivy
1 CVE-2026-54276
Files: uv.lock · reported by trivy
1 CVE-2026-54277
Files: uv.lock · reported by trivy
1 CVE-2026-54278
Files: uv.lock · reported by trivy
1 CVE-2026-54279
Files: uv.lock · reported by trivy
1 CVE-2026-54280
Files: uv.lock · reported by trivy
1 CVE-2026-55443
Files: uv.lock · reported by trivy
1 CVE-2026-59881
Files: uv.lock · reported by trivy
1 CVE-2026-59884
Files: uv.lock · reported by trivy
1 CVE-2026-59885
Files: uv.lock · reported by trivy
1 CVE-2026-59886
Files: uv.lock · reported by trivy
1 CVE-2026-59939
Files: uv.lock · reported by trivy
1 CVE-2026-69243
Files: uv.lock · reported by trivy
1 CVE-2026-69244
Files: uv.lock · reported by trivy
1 GHSA-6v7p-g79w-8964
Files: uv.lock · reported by trivy
1 PYSEC-2026-107
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1097
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1099
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1100
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1101
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1104
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1105
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1106
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1107
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1109
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-141
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1515
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1518
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1520
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1527
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1605
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-1810
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1845
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1872
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-2094
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2095
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2096
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2097
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2098
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2099
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2100
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2101
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2102
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2103
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2104
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2105
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2106
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2107
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2109
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2110
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2111
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2112
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2113
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-215
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2192
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2193
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2194
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2263
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-237
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2555
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2562
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2563
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2564
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2573
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2574
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2575
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2582
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2583
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3444
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3455
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3456
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3457
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-348
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3545
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3546
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3547
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3625
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-373
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-77
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-83
Files: /repo/uv.lock · reported by osv-scanner
5 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: DATA_EXFIL_NETWORK_REQUESTS, TOOL_ABUSE_UNDECLARED_NETWORK, SOCIAL_ENG_VAGUE_DESCRIPTION and 1 more · Files: /repo/src/bot/commands/put.py, /repo/src/bot/tools/work_tools/file_receiver.py, /repo/repo/README.md and 1 more · reported by cisco-skill-scanner
1 The model did not answer for these findings.
Rules: PYSEC-2026-2108 · Files: /repo/uv.lock · reported by osv-scanner
Critical vulnerabilities and network egress risks identified.
The artifact contains critical vulnerabilities in its dependencies, identified by `osv-scanner` and `trivy` in `uv.lock`. High-severity findings indicate potential for network egress, including secret data transmission, and Server-Side Request Forgery (SSRF) in `uv.lock`. Numerous high-severity findings from `bearer` point to potential sensitive operations within application code, such as file handling and command execution, and `cisco-skill-scanner` identified potential resource abuse.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Showing 7 of 7; the rest are in the per-scanner reports above.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.