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 -- teastream-backend
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.
v1.4.0
2 findings · 0.7s
v2.0.11
60 findings · 18.4s
v0.3.74
1 finding · 20.1s
v0.1.0
0 findings · 8.8s
v0.1.0
0 findings · 8.8s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.2s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 1.7s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 22, 2026 | Scan Halted | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicable | rejected |
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 63 findings across every scanner that examined this package.
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.
20 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: /repo/docs/SKILL.md, /repo/docs/onboarding/SKILL.md, /repo/docs/decisions/SKILL.md and 7 more · reported by cisco-skill-scanner
2 CI or editor configuration — The match is in build, CI or editor configuration, confirmed by our own check to be outside the installed artifact.
Rules: permissions-no-block, hooks-no-pretooluse · Files: .vscode/settings.json · reported by agentshield
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.
13 LOW_ANALYZABILITY
Files: /repo/src/modules/category, /repo/src/modules/follow, /repo/src/modules/webhook and 10 more · reported by cisco-skill-scanner
13 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/src/core/SKILL.md, /repo/src/modules/notification/SKILL.md and 10 more · reported by cisco-skill-scanner
13 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/src/core/SKILL.md, /repo/src/modules/notification/SKILL.md and 10 more · reported by cisco-skill-scanner
1 AAK-SECRET-004
Files: src/modules/libs/telegram/telegram.service.ts · reported by agent-audit-kit
1 EXCESSIVE_FILE_COUNT
Files: /repo/. · reported by cisco-skill-scanner
Exposed secret and high code analysis difficulty
An exposed secret in `src/modules/libs/telegram/telegram.service.ts` could lead to unauthorized access or use of a Telegram service. Additionally, a substantial portion of the installed code, including core components and several modules, exhibits low analyzability. This low analyzability across many directories, such as `src/modules/auth` and `src/modules/chat`, means that potential risks within these areas cannot be fully assessed by automated scanners.
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.