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 -- good-humans-inc/mvp
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
2 findings · 9.4s
v0.3.74
2 findings · 33.3s
v0.1.0
6 findings · 6.3s
v0.1.0
0 findings · 6.3s
v0.71.0
35 findings · 0.3s
v2.3.8
38 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
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.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 | 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 83 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 2 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.
9 CVE-2024-35195
Files: backend/generate_exercise/requirements.txt, backend/generate_report/requirements.txt, backend/monitor_notification_changes/requirements.txt and 6 more · reported by trivy
9 CVE-2024-47081
Files: backend/generate_exercise/requirements.txt, backend/generate_report/requirements.txt, backend/monitor_notification_changes/requirements.txt and 6 more · reported by trivy
9 CVE-2026-25645
Files: backend/generate_exercise/requirements.txt, backend/generate_report/requirements.txt, backend/monitor_notification_changes/requirements.txt and 6 more · reported by trivy
9 PYSEC-2026-1872
Files: /repo/backend/generate_exercise/requirements.txt, /repo/backend/generate_report/requirements.txt, /repo/backend/monitor_notification_changes/requirements.txt and 6 more · reported by osv-scanner
9 PYSEC-2026-1873
Files: /repo/backend/generate_exercise/requirements.txt, /repo/backend/generate_report/requirements.txt, /repo/backend/monitor_notification_changes/requirements.txt and 6 more · reported by osv-scanner
9 PYSEC-2026-2275
Files: /repo/backend/generate_exercise/requirements.txt, /repo/backend/generate_report/requirements.txt, /repo/backend/monitor_notification_changes/requirements.txt and 6 more · reported by osv-scanner
6 opt.nerlo-rules.nerlo-py-secret-to-network-egress
Files: /repo/backend/generate_exercise/main.py, /repo/backend/send_notification/main.py, /repo/backend/test_notification/main.py · reported by nerlo-behavioral
2 PYSEC-2026-1805
Files: /repo/backend/analyze_exercise_poses/requirements.txt, /repo/backend/monitor_notification_changes/requirements.txt · reported by osv-scanner
2 PYSEC-2026-1806
Files: /repo/backend/analyze_exercise_poses/requirements.txt, /repo/backend/monitor_notification_changes/requirements.txt · reported by osv-scanner
1 AAK-TASKS-003
Files: backend/schedule_notification/main.py · reported by agent-audit-kit
1 AAK-TASKS-004
Files: backend/schedule_notification/main.py · reported by agent-audit-kit
1 CVE-2024-1681
Files: backend/update_fcm_token/requirements.txt · reported by trivy
1 CVE-2024-6221
Files: backend/update_fcm_token/requirements.txt · reported by trivy
1 CVE-2024-6839
Files: backend/update_fcm_token/requirements.txt · reported by trivy
1 CVE-2024-6844
Files: backend/update_fcm_token/requirements.txt · reported by trivy
1 CVE-2024-6866
Files: backend/update_fcm_token/requirements.txt · reported by trivy
1 CVE-2025-4565
Files: backend/monitor_notification_changes/requirements.txt · reported by trivy
1 CVE-2026-0994
Files: backend/monitor_notification_changes/requirements.txt · reported by trivy
1 CVE-2026-27205
Files: backend/update_fcm_token/requirements.txt · reported by trivy
1 PYSEC-2024-271
Files: /repo/backend/update_fcm_token/requirements.txt · reported by osv-scanner
1 PYSEC-2024-71
Files: /repo/backend/update_fcm_token/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1383
Files: /repo/backend/update_fcm_token/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1384
Files: /repo/backend/update_fcm_token/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1385
Files: /repo/backend/update_fcm_token/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2151
Files: /repo/backend/update_fcm_token/requirements.txt · reported by osv-scanner
1 PYSEC-2026-899
Files: /repo/backend/analyze_exercise_poses/requirements.txt · reported by osv-scanner
2 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: /repo/backend/utils/SKILL.md · reported by cisco-skill-scanner
Artifact has network egress, credential access risks, and critical vulnerabilities.
The artifact exhibits potential for network egress of secrets from `generate_exercise`, `send_notification`, and `test_notification` components. Credential access risks are also present in `logging_update_tool.py`. Additionally, multiple high-severity vulnerabilities exist in dependencies across several backend components, including `analyze_exercise_poses` and `monitor_notification_changes`.
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.