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.
1 critical finding reported by cisco-skill-scanner, 0 of them in the installed artifact. The composite score alone does not reflect this — read the per-scanner reports below.
github_release: https://github.com/yashiels/twitter-cli, 0 findings
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 -- twitter-cli
9 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 · 7.8s
v0.3.74
6 findings · 1.1s
v0.1.0
1 finding · 3.7s
v0.1.0
0 findings · 3.8s
vv0.3.2
Incomplete run
0 findings · 2.5s
v0.1.0
0 findings · 9.8s
v0.71.0
1 finding · 0.3s
v2.3.8
11 findings · 0.8s
vv1.6.0
Incomplete run
0 findings · 1.8s
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.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 20, 2026 | Flagged89 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·!: incompletenerlo-multi-source: completetrivy: completeosv-scanner: completetrivy_image ·n/a: not applicablegovulncheck ·!: incomplete | 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 30 findings across every scanner that examined this package. None of the 1 finding 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.
5 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, MANIFEST_INVALID_NAME · Files: /repo/.github/SKILL.md, /repo/docs/SKILL.md · 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: AAK-GHA-IMMUTABLE-001 · Files: .github/workflows/pr-agent.yml, .github/workflows/release.yml · reported by agent-audit-kit
1 Agent instruction file — The match is in a file that instructs an AI coding agent — a CLAUDE.md or similar. It is documentation of intent, and our own check confirmed it is not part of what gets installed.
Rules: AAK-AGENT-002 · Files: AGENTS.md · reported by agent-audit-kit
The model could have called any of these a false positive and did not.
3 AAK-SECRET-004
Files: internal/api/client.go, internal/auth/chrome.go · reported by agent-audit-kit
2 GO-2026-5932
Files: go.mod, /repo/go.mod · reported by trivy, osv-scanner
1 GO-2026-4970
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-5026
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-5856
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-5942
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-5972
Files: /repo/go.mod
6 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: YARA_coercive_injection_generic, SOCIAL_ENG_VAGUE_DESCRIPTION, HIDDEN_DATA_FILE and 1 more · Files: /repo/skill/SKILL.md, /repo/SKILL.md, /repo/.golangci.yml and 1 more · reported by cisco-skill-scanner
Critical injection risk and credential exposure detected
A critical finding indicates potential coercive injection in `/repo/skill/SKILL.md`. Multiple high severity findings point to credential exposure within `internal/api/client.go` and `internal/auth/chrome.go`. This artifact carries risks related to code injection and sensitive credential exposure.
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.
1 GO-2026-6088
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-6089
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-6090
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-6091
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-6218
Files: /repo/go.mod · reported by osv-scanner
1 opt.nerlo-rules.nerlo-go-hardcoded-external-egress
Files: /repo/internal/api/verify.go · reported by nerlo-behavioral