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 agent-audit-kit. 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 -- mahjong_score
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
Incomplete run
0 findings · 1.0s
v2.0.11
37 findings · 7.7s
v0.3.74
12 findings · 2.1s
v0.1.0
0 findings · 3.1s
v0.1.0
0 findings · 3.1s
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 · 0.9s
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 20, 2026 | Scan Halted | — | agentshield ·!: incompletecisco-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 49 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 21 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 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/.github/SKILL.md, /repo/docs/SKILL.md · reported by cisco-skill-scanner
2 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: FILE_MAGIC_MISMATCH · Files: /repo/frontend/CLAUDE.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, MANIFEST_INVALID_NAME · Files: .github/workflows/ci.yml, /repo/.github/SKILL.md · reported by agent-audit-kit, cisco-skill-scanner
1 Placeholder value — The matched literal is a placeholder or example — the kind of value a scanner reads as a secret and a human reads as a blank to fill in.
Rules: HIDDEN_DATA_FILE · Files: /repo/frontend/.env.local.example · reported by cisco-skill-scanner
The model could have called any of these a false positive and did not.
3 FILE_MAGIC_MISMATCH
Files: /repo/config/database.yml, /repo/config/storage.yml, /repo/config/initializers/version.rb · reported by cisco-skill-scanner
3 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/.claude/SKILL.md, /repo/frontend/SKILL.md · reported by cisco-skill-scanner
2 AAK-LEGAL-002
Files: package.json, frontend/package.json · reported by agent-audit-kit
2 AAK-MCP-005
Files: .mcp.json · reported by agent-audit-kit
2 AAK-MCP-007
Files: .mcp.json · reported by agent-audit-kit
2 AAK-MCP-ATTEST-001
Files: .mcp.json · reported by agent-audit-kit
2 AAK-SUPPLY-001
21 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: AAK-TRUST-001, DATA_EXFIL_JS_NETWORK, SOCIAL_ENG_VAGUE_DESCRIPTION and 2 more · Files: .claude/settings.json, /repo/frontend/app/lib/api.ts, /repo/SKILL.md and 16 more · reported by agent-audit-kit, cisco-skill-scanner
Critical trust issue and supply chain risks identified.
The artifact contains a critical trust finding in `.claude/settings.json`, which could lead to credential exposure or insecure system configuration. High severity supply chain risks are also present within `.mcp.json`, potentially introducing arbitrary code execution or data exfiltration. Additionally, parts of the frontend code exhibit low analyzability, which may obscure other security concerns.
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.
Files: .mcp.json · reported by agent-audit-kit
2 LOW_ANALYZABILITY
Files: /repo/frontend, /repo · reported by cisco-skill-scanner
1 EXCESSIVE_FILE_COUNT
Files: /repo/. · reported by cisco-skill-scanner