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 -- mgd1984/the-way-of-code
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
14 findings · 6.4s
v0.3.74
5 findings · 1.2s
v0.1.0
0 findings · 2.8s
v0.1.0
0 findings · 2.8s
v0.71.0
1 finding · 0.2s
v2.3.8
24 findings · 6.4s
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 · 0.8s
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 | Flagged64 | — | 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 44 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 40 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.
3 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: MANIFEST_MISSING_LICENSE · Files: /repo/docs/SKILL.md, /repo/examples/scenarios/SKILL.md, /repo/examples/prompts/SKILL.md · reported by cisco-skill-scanner
The model could have called any of these a false positive and did not.
1 GHSA-4x5r-pxfx-6jf8
Files: /repo/mcp-server/pnpm-lock.yaml · reported by osv-scanner
36 The review call did not complete.
Rules: GHSA-7r86-cg39-jmmj, GHSA-mh99-v99m-4gvg, GHSA-3ppc-4f35-3m26 and 20 more · Files: /repo/mcp-server/pnpm-lock.yaml, .cursor/mcp.json, /repo/mcp-server and 9 more · reported by osv-scanner, agent-audit-kit, cisco-skill-scanner and 1 more
4 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: AAK-MCP-007, MANIFEST_MISSING_LICENSE · Files: .cursor/mcp.json, /repo/SKILL.md, /repo/mcp-server/SKILL.md and 1 more · reported by agent-audit-kit, cisco-skill-scanner
Multiple high severity vulnerabilities in dependencies and code.
The artifact contains multiple high-severity vulnerabilities in its dependencies, identified in `/repo/mcp-server/pnpm-lock.yaml`. These vulnerabilities could enable remote code execution, denial of service, or information disclosure. A supply chain risk was also identified in `.cursor/mcp.json`, and low analyzability in `/repo/mcp-server` requires further investigation.
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.