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 -- assembled-dashboard
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
1 finding · 0.9s
v2.0.11
23 findings · 11.3s
v0.3.74
5 findings · 5.1s
v0.1.0
0 findings · 5.5s
v0.1.0
0 findings · 5.6s
v0.71.0
39 findings · 0.4s
v2.3.8
44 findings · 8.0s
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.9s
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 | Flagged40 | — | 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 112 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.
1 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: secrets-base64-obfuscation-17677 · Files: CLAUDE.md · reported by 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.
9 MANIFEST_MISSING_LICENSE
Files: /repo/.claude/skills/make-responsive/SKILL.md, /repo/.claude/skills/ideas/SKILL.md, /repo/.claude/skills/design/SKILL.md and 6 more · reported by cisco-skill-scanner
5 AAK-LEGAL-002
Files: package.json, packages/eslint-config/package.json, packages/ui/package.json and 2 more · reported by agent-audit-kit
4 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/.wayfinder/SKILL.md, /repo/packages/typescript-config/SKILL.md and 1 more · reported by cisco-skill-scanner
3 DATA_EXFIL_JS_NETWORK
Files: /repo/apps/web/hooks/use-dashboard-data.ts · reported by cisco-skill-scanner
3 GHSA-fxqj-rqcc-2cmp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
3 GHSA-r28c-9q8g-f849
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 CVE-2026-69153
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-73646
Files: pnpm-lock.yaml · reported by trivy
2 FILE_MAGIC_MISMATCH
Files: /repo/apps/storybook/.storybook/preview-head.html, /repo/DESIGN.md · reported by cisco-skill-scanner
2 GHSA-3jxr-9vmj-r5cp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-5p4m-2wfm-xmqj
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
2 GHSA-f88m-g3jw-g9cj
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
2 GHSA-frvp-7c67-39w9
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
2 GHSA-mh99-v99m-4gvg
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-rgw5-rvv9-x895
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 LOW_ANALYZABILITY
Files: /repo/packages/eslint-config, /repo · reported by cisco-skill-scanner
1 CVE-2026-13149
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-13697
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-14257
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-14643
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-15157
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-16221
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-16728
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-16729
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-18446
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-53550
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-54272
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59869
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64641
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64642
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-69152
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 EXCESSIVE_FILE_COUNT
Files: /repo/. · reported by cisco-skill-scanner
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-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-4cwx-7wf7-3272
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-52cp-r559-cp3m
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-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-6gpp-xcg3-4w24
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-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-8xcm-r25x-g524
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-f23p-vx2j-j53r
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-jr45-8vmc-qm54
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-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-v2hh-gcrm-f6hx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v3r7-h72x-cjcm
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 HIDDEN_DATA_FILE
Files: /repo/.wayfinder/map.md · reported by cisco-skill-scanner
1 MANIFEST_INVALID_NAME
Files: /repo/.wayfinder/SKILL.md · reported by cisco-skill-scanner
Artifact contains numerous high-severity vulnerabilities and potential network egress.
This artifact contains numerous high-severity vulnerabilities identified in its dependencies, primarily within `pnpm-lock.yaml`. It also exhibits potential for network egress from JavaScript code. Furthermore, parts of the artifact, specifically `/repo` and `/repo/packages/eslint-config`, have low analyzability, hindering a full security assessment.
Concern level assessed by the review: High. This is the review's scale, not the registry badge.
Showing 25 of 44; 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.