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.
2 critical findings reported by osv-scanner. The composite score alone does not reflect this — read the per-scanner reports below.
npm: llm-wiki @ 0.1.0, 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 -- llm-wiki
8 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 · 1.6s
v2.0.11
23 findings · 18.2s
v0.3.74
7 findings · 4.5s
v0.1.0
0 findings · 6.0s
v0.1.0
1 finding · 6.0s
v0.1.0
0 findings · 11.8s
v0.71.0
40 findings · 0.5s
v2.3.8
60 findings · 12.0s
vv0.3.2
No Go packages 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
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 | Flagged42 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source: completetrivy: 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 133 findings across every scanner that examined this package. None of the 2 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 15 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.
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: MANIFEST_INVALID_NAME, MANIFEST_MISSING_LICENSE · Files: /repo/.github/SKILL.md · reported by cisco-skill-scanner
1 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 · Files: /repo/.github/SKILL.md · reported by cisco-skill-scanner
The model could have called any of these a false positive and did not.
10 MANIFEST_MISSING_LICENSE
Files: /repo/.claude/skills/wiki-lint/SKILL.md, /repo/.claude/skills/wiki-query/SKILL.md, /repo/.claude/skills/wiki-ingest/SKILL.md and 7 more · reported by cisco-skill-scanner
3 GHSA-5p4m-2wfm-xmqj
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
2 EXCESSIVE_FILE_COUNT
Files: /repo/wiki/., /repo/. · reported by cisco-skill-scanner
2 GHSA-3jxr-9vmj-r5cp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-52cp-r559-cp3m
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-67mh-4wv8-2f99
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2
14 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: AAK-HOOK-004, permissions-no-block, AAK-HEALTHCARE-AI-004 and 2 more · Files: .claude/settings.json, settings.json, wiki/index.md and 8 more · reported by agent-audit-kit, agentshield, cisco-skill-scanner and 1 more
1 The model did not answer for these findings.
Rules: GHSA-f88m-g3jw-g9cj · Files: pnpm-lock.yaml · reported by trivy
Critical vulnerabilities in dependencies detected.
This artifact contains critical vulnerabilities, specifically GHSA-5xrq-8626-4rwp and GHSA-w7jw-789q-3m8p, found in its dependencies. Numerous high-severity vulnerabilities are also present in dependencies, including GHSA-mh99-v99m-4gvg and GHSA-r28c-9q8g-f849. Additionally, high-severity findings related to AAK-HOOK-004 are noted in .claude/settings.json.
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: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
2 GHSA-fxqj-rqcc-2cmp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-g7r4-m6w7-qqqr
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-h67p-54hq-rp68
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-mh99-v99m-4gvg
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-r28c-9q8g-f849
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-rgw5-rvv9-x895
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 AAK-LEGAL-002
Files: package.json · reported by agent-audit-kit
1 AAK-MCP-018
Files: src/lib/mcp/tools.ts · reported by agent-audit-kit
1 AAK-OAUTH-3P-001
Files: package.json · reported by agent-audit-kit
1 CVE-2026-12590
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-13676
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-16221
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-18446
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-39356
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-41305
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-45623
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-48779
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-53550
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-54272
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-54286
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-54287
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-54288
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-54289
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-54290
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59869
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59895
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59896
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59897
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64641
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64643
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64644
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64645
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64646
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64647
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64648
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64649
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-67213
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-67214
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-69153
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-69192
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-69198
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-69207
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-71848
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-71849
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-71850
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-73646
Files: pnpm-lock.yaml · reported by trivy
1 GHSA-22jq-vg5j-6vgg
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-28wg-ghj8-5hjv
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2v37-7h3g-55p8
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-395f-4hp3-45gv
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4633-3j49-mh5q
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4c39-4ccg-62r3
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4c8g-83qw-93j6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4xrf-jv44-h6hh
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-54fx-42gc-7vw4
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-5xrq-8626-4rwp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-68g3-v927-f742
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-6g55-p6wh-862q
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-79qm-7rj5-m7r9
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-7p8r-x3mc-p8w7
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-88fw-hqm2-52qc
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-89xv-2m56-2m9x
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8j4g-w8fx-2239
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-955p-x3mx-jcvp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-96hv-2xvq-fx4p
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-f23p-vx2j-j53r
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-f88m-g3jw-g9cj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-fx2h-pf6j-xcff
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-gpj5-g38j-94v9
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-hvrm-45r6-mjfj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-j6c9-x7qj-28xf
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-m99w-x7hq-7vfj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mwp4-54f8-5fhr
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-p9j2-gv94-2wf4
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-q8wf-6r8g-63ch
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-qx2v-qp2m-jg93
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-rv63-4mwf-qqc2
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v2hh-gcrm-f6hx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v422-hmwv-36x6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v6wh-96g9-6wx3
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-w62v-xxxg-mg59
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-w7jw-789q-3m8p
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-wgpf-jwqj-8h8p
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-wwfh-h76j-fc44
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-xgm2-5f3f-mvvc
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
Showing 25 of 25; the rest are in the per-scanner reports above.