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 trivy, osv-scanner. 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 -- root
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
2 findings · 0.7s
v2.0.11
76 findings · 15.3s
v0.3.74
11 findings · 5.3s
v0.1.0
0 findings · 5.9s
v0.1.0
15 findings · 5.9s
v0.71.0
43 findings · 0.4s
v2.3.8
72 findings · 8.4s
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 · 1.0s
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 | Flagged36 | — | 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 219 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 4 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.
33 Test or fixture file — The match is in a test or fixture. Our own check confirmed the file is not part of what gets installed.
Rules: LOW_ANALYZABILITY, DATA_EXFIL_JS_NETWORK, FILE_MAGIC_MISMATCH and 1 more · Files: /repo/playgrounds/prometheus-astro6/e2e, /repo/playgrounds/prometheus/e2e, /repo/playgrounds/prometheus-astro5/e2e and 7 more · reported by cisco-skill-scanner, agent-audit-kit
11 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: AAK-LEGAL-002, opt.nerlo-rules.nerlo-install-run-bundled-artifact, MANIFEST_MISSING_LICENSE · Files: demo/package.json, /repo/playgrounds/prometheus-astro5/e2e/README.md, /repo/playgrounds/prometheus-astro6/e2e/README.md and 5 more · reported by agent-audit-kit, nerlo-install-instruction, cisco-skill-scanner
5 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, permissions-no-block, hooks-no-pretooluse · Files: .github/workflows/ci.yml, .github/workflows/pr-validation.yml, .github/workflows/release.yml and 1 more · reported by agent-audit-kit, agentshield
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.
10 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/.changeset/SKILL.md, /repo/playgrounds/SKILL.md and 7 more · reported by cisco-skill-scanner
10 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/.changeset/SKILL.md, /repo/playgrounds/SKILL.md and 7 more · reported by cisco-skill-scanner
9 opt.nerlo-rules.nerlo-install-run-bundled-artifact
Files: /repo/playgrounds/prometheus-astro5/E2E_TESTING_SUMMARY.md, /repo/playgrounds/prometheus-astro5/E2E_WORKFLOW_QUICK_REFERENCE.md, /repo/playgrounds/prometheus-astro6/E2E_TESTING_SUMMARY.md and 3 more · reported by nerlo-install-instruction
8 LOW_ANALYZABILITY
Files: /repo/playgrounds/prometheus-astro6, /repo/playgrounds/prometheus-astro5, /repo/packages/astro-opentelemetry-integration and 5 more · reported by cisco-skill-scanner
5 AAK-LEGAL-002
Files: package.json, playgrounds/otel/package.json, playgrounds/prometheus-astro6/package.json and 2 more · reported by agent-audit-kit
3 GHSA-5p4m-2wfm-xmqj
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
3 HIDDEN_DATA_FILE
Files: /repo/.changeset/prom-client-peer-dependency.md, /repo/.changeset/config.json, /repo/.changeset/README.md · reported by cisco-skill-scanner
2 CVE-2026-44288
Files: pnpm-lock.yaml · reported by trivy
2 EXCESSIVE_FILE_COUNT
Files: /repo/., /repo/playgrounds/. · reported by cisco-skill-scanner
2 FILE_MAGIC_MISMATCH
Files: /repo/packages/astro-prometheus-node-integration/vitest.setup.ts · reported by cisco-skill-scanner
2 GHSA-23c5-xmqv-rm74
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-4g3v-8h47-v7g6
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-7pw4-f3q4-r2p2
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-7r86-cg39-jmmj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-f48w-9m4c-m7f5
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-f88m-g3jw-g9cj
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
2 GHSA-g7r4-m6w7-qqqr
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
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-q6x5-8v7m-xcrf
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-r557-wffq-wvrc
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-rgw5-rvv9-x895
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-v3rj-xjv7-4jmq
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
1 AAK-SUPPLY-003
Files: package.json · reported by agent-audit-kit
1 CVE-2025-64756
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-66400
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-27606
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-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-41242
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44289
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44290
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44291
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44292
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44293
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44294
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-45740
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-48068
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-48069
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-48712
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-53550
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-53571
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-53632
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-54269
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59727
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59729
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59730
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59869
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59877
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-67213
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-73422
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-73646
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-73650
Files: pnpm-lock.yaml · reported by trivy
1 GHSA-2g4f-4pwh-qvx6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2p49-hgcm-8545
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2pr8-phx7-x9h3
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2pvr-wf23-7pc7
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-3ppc-4f35-3m26
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3rmj-9m5h-8fpv
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-4c8g-83qw-93j6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4fh9-h7wg-q85m
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-5375-pq7m-f5r2
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-66ff-xgx4-vchm
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-685m-2w69-288q
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-75px-5xx7-5xc7
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-8hv8-536x-4wqp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-99f4-grh7-6pcq
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-c57f-mm3j-27q9
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-f38q-mgvj-vph7
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-fx83-v9x8-x52w
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-j3f2-48v5-ccww
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-j687-52p2-xcff
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-jggg-4jg4-v7c6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-jrpj-wcv7-9fh9
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-jvwf-75h9-cwgg
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-jxxr-4gwj-5jf2
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-mw96-cpmx-2vgc
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-q3j6-qgpj-74h6
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-v2hh-gcrm-f6hx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v39h-62p7-jpjc
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-wcpc-wj8m-hjx6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-xq3m-2v4x-88gg
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-xr5h-phrj-8vxv
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 MANIFEST_INVALID_NAME
Files: /repo/.changeset/SKILL.md · reported by cisco-skill-scanner
4 The model did not answer for these findings.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION · Files: /repo/demo/SKILL.md, /repo/playgrounds/prometheus-astro6/e2e/SKILL.md, /repo/playgrounds/prometheus/e2e/SKILL.md and 1 more · reported by cisco-skill-scanner
Critical vulnerabilities found in artifact dependencies.
The artifact contains critical vulnerabilities in its dependencies, specifically identified in `pnpm-lock.yaml`. These issues could potentially lead to severe impacts such as remote code execution or data compromise. Additionally, numerous high-severity vulnerabilities are present across various components, including those related to `pnpm-lock.yaml` and several `/repo` subdirectories. These findings warrant immediate and thorough investigation before deployment.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Showing 25 of 70; the rest are in the per-scanner reports above.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.