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 -- keyword-assistant
7 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
0 findings · 1.6s
v2.0.11
9 findings · 11.1s
v0.3.74
2 findings · 2.8s
v0.1.0
0 findings · 5.1s
v0.1.0
0 findings · 5.1s
v0.71.0
18 findings · 0.4s
v2.3.8
59 findings · 11.0s
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 · 2.4s
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 21, 2026 | Flagged45 | — | agentshield: completecisco-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 88 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.
2 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 · reported by cisco-skill-scanner
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.
3 GHSA-23c5-xmqv-rm74
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
3 GHSA-3ppc-4f35-3m26
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
3 GHSA-7r86-cg39-jmmj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3jxr-9vmj-r5cp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-f886-m6hf-6m8v
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-mw96-cpmx-2vgc
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2
Multiple high-severity vulnerabilities and exposed secrets detected.
The artifact contains numerous high-severity vulnerabilities in its dependencies, as indicated by multiple GHSA and CVE findings in pnpm-lock.yaml. Additionally, a high-severity finding (AAK-SECRET-004) indicates the presence of an exposed secret within `src/utils/keywords.ts`. These issues collectively present a significant risk, including potential for credential access and exploitation through vulnerable components.
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.
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-v6h2-p8h4-qcjw
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 AAK-LEGAL-002
Files: package.json · reported by agent-audit-kit
1 AAK-SECRET-004
Files: src/utils/keywords.ts · reported by agent-audit-kit
1 BINARY_FILE_DETECTED
Files: /repo/.DS_Store · reported by cisco-skill-scanner
1 CVE-2025-5889
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-64756
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-13149
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-14257
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-26996
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-27903
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-27904
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33532
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33671
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33672
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33750
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-67213
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-67214
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-69152
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-69153
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-73646
Files: pnpm-lock.yaml · reported by trivy
1 FILE_MAGIC_MISMATCH
Files: /repo/src/utils/platform.ts · reported by cisco-skill-scanner
1 GHSA-25h7-pfq9-p65f
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-2g4f-4pwh-qvx6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2mjp-6q6p-2qxm
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-35p6-xmwp-9g52
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3v7f-55p6-f55p
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-48c2-rrv3-qjmp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4992-7rv2-5pvq
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4w7w-66w2-5vf9
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4x5r-pxfx-6jf8
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-52cp-r559-cp3m
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-5j98-mcp5-4vw2
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-5p4m-2wfm-xmqj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-67mh-4wv8-2f99
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-8xcm-r25x-g524
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-93m4-6634-74q7
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-c2c7-rcm5-vvqj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-f269-vfmq-vjvj
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-fxqj-rqcc-2cmp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-g4jq-h2w9-997c
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-g8m3-5g58-fq7m
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-g9mf-h72j-4rw9
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-h67p-54hq-rp68
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-jqfw-vq24-v9c3
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-m8rv-5g2x-5cg5
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mh29-5h37-fv8m
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-p88m-4jfj-68fv
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-r28c-9q8g-f849
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-rf6f-7fwh-wjgh
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v3r7-h72x-cjcm
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-v9p9-hfj2-hcw8
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-vrm6-8vpv-qv8q
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-vxpw-j846-p89q
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 HIDDEN_DATA_FILE
Files: /repo/.DS_Store · reported by cisco-skill-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
1 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 UNANALYZABLE_BINARY
Files: /repo/.DS_Store · reported by cisco-skill-scanner
Showing 25 of 46; the rest are in the per-scanner reports above.