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 -- enzosv/idlefit-flutter
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.
v2.0.11
16 findings · 7.0s
v0.3.74
0 findings · 1.2s
v0.1.0
0 findings · 2.8s
v0.71.0
0 findings · 0.3s
v2.3.8
0 findings · 0.2s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
v0.1.0
No source files this scanner can analyze were found in this artifact. What each scanner covers
0 findings · 2.8s
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 | Flagged92 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral ·n/a: not applicablenerlo-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 16 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 11 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.
1 ASSET_PROMPT_INJECTION
Files: /repo/assets/coin_generators copy.json · reported by cisco-skill-scanner
1 BINARY_FILE_DETECTED
Files: /repo/assets/lottie/walk.lottie · reported by cisco-skill-scanner
1 EXCESSIVE_FILE_COUNT
Files: /repo/. · reported by cisco-skill-scanner
1 HIDDEN_DATA_FILE
Files: /repo/.metadata · reported by cisco-skill-scanner
1 UNANALYZABLE_BINARY
Files: /repo/assets/lottie/walk.lottie · reported by cisco-skill-scanner
11 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: FILE_MAGIC_MISMATCH, SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE and 1 more · Files: /repo/linux/CMakeLists.txt, /repo/linux/flutter/CMakeLists.txt, /repo/linux/runner/CMakeLists.txt and 5 more · reported by cisco-skill-scanner
Prompt injection, unanalyzable binary components detected.
The artifact contains components susceptible to prompt injection, which could lead to unintended execution or data exposure. An unanalyzable binary component prevents full security assessment, and file type mismatches suggest potential obfuscation. The presence of hidden data files also warrants attention.
Concern level assessed by the review: Medium. 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.