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.
14 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 -- mahdi-portfolio-nuxt
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 · 0.9s
v2.0.11
591 findings · 22.5s
v0.3.74
9 findings · 7.6s
v0.1.0
0 findings · 5.5s
v0.1.0
2 findings · 5.5s
v0.71.0
135 findings · 1.1s
v2.3.8
141 findings · 8.5s
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.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 22, 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 878 findings across every scanner that examined this package. None of the 14 findings rated critical by their scanner were dismissed.
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.
69 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: AAK-HEALTHCARE-AI-004, LAZY_LOAD_DEEP_NESTING, SOCIAL_ENG_VAGUE_DESCRIPTION and 2 more · Files: .bmad/bmm/docs/party-mode.md, .bmad/bmm/docs/test-architecture.md, .bmad/bmm/docs/agents-guide.md and 54 more · reported by agent-audit-kit, cisco-skill-scanner
2 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: HIDDEN_DATA_FILE · Files: /repo/.bmad/docs/codex-instructions.md, /repo/.bmad/docs/roo-instructions.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.
343 HIDDEN_DATA_FILE
Files: /repo/.agent/workflows/bmad/bmad-bmm-agents-quick-flow-solo-dev.md, /repo/.bmad/bmm/testarch/knowledge/risk-governance.md, /repo/.bmad/core/workflows/party-mode/steps/step-03-graceful-exit.md and 340 more · reported by cisco-skill-scanner
66 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/content/SKILL.md, /repo/content/fa/blog/SKILL.md and 63 more · reported by cisco-skill-scanner
53 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/content/SKILL.md, /repo/.bmad/bmm/SKILL.md and 50 more · reported by cisco-skill-scanner
42 FILE_MAGIC_MISMATCH
Files: /repo/.bmad/bmm/workflows/document-project/workflows/deep-dive-instructions.md, /repo/.bmad/bmm/workflows/document-project/templates/index-template.md, /repo/.bmad/bmm/workflows/document-project/templates/project-overview-template.md and 10 more · reported by cisco-skill-scanner
6 DATA_EXFIL_JS_FS_ACCESS
Files: /repo/nuxt-ssg-diagnostic.cjs, /repo/scripts/check-i18n.mjs, /repo/scripts/check-portfolio-data.mjs · reported by cisco-skill-scanner
4 CVE-2026-26996
Files: pnpm-lock.yaml · reported by trivy
4 CVE-2026-27903
Files: pnpm-lock.yaml · reported by trivy
4 CVE-2026-27904
Files: pnpm-lock.yaml · reported by trivy
4 GHSA-23c5-xmqv-rm74
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-3ppc-4f35-3m26
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-7r86-cg39-jmmj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
4 YARA_autonomy_abuse_generic
Files: /repo/.bmad/bmm/workflows/1-analysis/product-brief/steps/SKILL.md · reported by cisco-skill-scanner
3 AAK-HEALTHCARE-AI-004
Files: .bmad/bmm/agents/tech-writer.md, .bmad/bmm/workflows/2-plan-workflows/prd/steps/step-05-domain.md, .bmad/bmm/workflows/2-plan-workflows/prd/steps/step-02-discovery.md · reported by agent-audit-kit
3 YARA_prompt_injection_unicode_steganography
Files: /repo/design templates/Ali_Arghyani_Resume.pdf · reported by cisco-skill-scanner
2 CVE-2026-13149
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-14257
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-29074
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-33671
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-33672
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-33750
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-45736
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-46342
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-47200
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-48779
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-53632
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-67214
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-69152
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-73650
Files: pnpm-lock.yaml · reported by trivy
2 EXCESSIVE_FILE_COUNT
Files: /repo/.bmad/bmm/., /repo/. · reported by cisco-skill-scanner
2 GHSA-28wg-ghj8-5hjv
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-2p49-hgcm-8545
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-33hq-fvwr-56pm
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
2 GHSA-3jxr-9vmj-r5cp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3v7f-55p6-f55p
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-4hxc-9384-m385
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
2 GHSA-534h-c3cw-v3h9
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
2 GHSA-58qx-3vcg-4xpx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-5c6j-r48x-rmvq
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
2 GHSA-5p4m-2wfm-xmqj
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
2 GHSA-6v7q-wjvx-w8wg
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
2 GHSA-72gr-qfp7-vwhw
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
2 GHSA-8qm3-746x-r74r
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
2 GHSA-96hv-2xvq-fx4p
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-c2c7-rcm5-vvqj
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-g8wj-3cr3-6w7v
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-gj2h-2fpw-fhv9
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
2 GHSA-hg3f-28rg-4jxj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-m3q2-p4fw-w38m
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-r292-9mhp-454m
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
2 GHSA-r4q5-vmmm-2653
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
2 GHSA-rgw5-rvv9-x895
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-rq7w-g337-39qq
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
2 GHSA-v6wh-96g9-6wx3
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-wr4h-v87w-p3r7
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
2 GHSA-xpqw-6gx7-v673
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 MANIFEST_INVALID_NAME
Files: /repo/.roo/commands/SKILL.md, /repo/.bmad/core/agents/SKILL.md · reported by cisco-skill-scanner
2 opt.nerlo-rules.nerlo-install-run-bundled-artifact
Files: /repo/.bmad/bmm/testarch/knowledge/ci-burn-in.md, /repo/.bmad/bmm/testarch/knowledge/contract-testing.md · reported by nerlo-install-instruction
2 UNANALYZABLE_BINARY
Files: /repo/design templates/Blue and White Clean and Professional Resume.pdf, /repo/design templates/Ali_Arghyani_Resume.pdf · reported by cisco-skill-scanner
1 AAK-IPI-WILD-CORPUS-001
Files: .bmad/bmm/testarch/knowledge/nfr-criteria.md · reported by agent-audit-kit
1 AAK-LEGAL-002
Files: package.json · reported by agent-audit-kit
1 AAK-SUPPLY-003
Files: package.json · reported by agent-audit-kit
1 CVE-2025-13465
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-69873
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-69874
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-13311
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-22774
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-22775
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-23527
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-23736
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-23737
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-23745
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-23950
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-23956
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-23957
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-24001
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-24006
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-24842
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-25547
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-26960
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-27606
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-27699
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-28291
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-28292
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-2950
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-29786
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-30226
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-31802
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-31860
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-31873
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-32141
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33128
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33151
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33228
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33532
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33732
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33891
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33894
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33895
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33896
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-34043
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-35209
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-39315
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-39363
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-39364
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-39365
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-41305
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-41324
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-42338
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44240
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44372
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44373
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-45623
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-45669
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-4800
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-49356
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-53655
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-53721
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-53722
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-56326
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-56876
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59869
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59871
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59873
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59874
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59875
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59940
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-67213
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-69153
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-69185
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-69192
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-6951
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-71314
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-71318
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-71319
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-71320
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-71321
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-73646
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-9277
Files: pnpm-lock.yaml · reported by trivy
1 GHSA-22cc-p3c6-wpvm
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2328-f5f3-gj25
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-23hp-3jrh-7fpw
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-25h7-pfq9-p65f
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-279x-mwfv-vcqv
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-2m8v-j782-fhvr
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-34x7-hfp2-rc4v
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-37qj-frw5-hhjh
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-3j22-8qj3-26mx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3rxj-6cgf-8cfw
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-48hr-524c-v5w3
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-5339-hvwr-7582
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-5m6q-g25r-mvwx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-5rq4-664w-9x2c
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-5w89-w975-hf9q
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-66fc-rw6m-c2q6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-677m-j7p3-52f9
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-737v-mqg7-c878
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-73rr-hh4g-fpgx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-7h2j-956f-4vf2
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-83g3-92jg-28cx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8gc5-j5rx-235r
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8qq5-rm4j-mr97
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8x88-c5mf-7j5w
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-92fh-27vv-894w
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-934w-87qh-qr26
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-9473-5f9j-94wq
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-95h2-gj7x-gx9w
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-9pgf-384g-p7mv
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-9phm-9p8f-hw5m
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-9ppj-qmqm-q256
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-c9cv-mq2m-ppp3
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-cfw5-2vxh-hr84
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-f23m-r3pf-42rh
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-fj3w-jwp8-x2g3
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-fx6j-w5w5-h468
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-g2pg-6438-jwpf
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-g5xx-pwrp-g3fv
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-gh4j-gqv2-49f6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-gvwx-54wh-qm9j
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-hffm-xvc3-vprc
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-hj76-42vx-jwp4
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-hx9m-jf43-8ffr
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-hxcr-hm88-mpq6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-jcxm-m3jx-f287
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-jmr7-xgp7-cmfj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-jmr9-qjv8-65gv
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-jp2q-39xq-3w4g
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-m7jm-9gc2-mpf2
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mm7m-92g8-7m47
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mp2g-9vg9-f4cg
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mv8w-475r-vwqw
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-mwp4-54f8-5fhr
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mwv9-gp5h-frr4
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-p36q-q72m-gchr
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-p9ff-h696-f583
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-ppp5-5v6c-4jwp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-q67f-28xg-22rw
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-qffp-2rhf-9h96
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-qj8w-gfj5-8c6v
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-r275-fr43-pm7q
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-r5fr-rjxr-66jc
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-r6q2-hw4h-h46w
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-rp42-5vxx-qpwr
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-rpmf-866q-6p89
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v2v4-37r5-5v8g
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v2wj-q39q-566r
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-vmf3-w455-68vh
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-vw5p-8cq8-m7mv
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-w8wr-v893-vjvp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
The model could have called any of these a false positive and did not.
1 GHSA-mwv9-gp5h-frr4
Files: pnpm-lock.yaml · reported by trivy
Critical vulnerabilities and file system access found in installed code.
The artifact contains 14 critical vulnerabilities identified in its dependency lock file (`pnpm-lock.yaml`). Additionally, multiple high-severity findings indicate potential file system access within `nuxt-ssg-diagnostic.cjs` and various scripts. These findings suggest the artifact's installed code may have capabilities for unauthorized file operations.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Showing 25 of 179; 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.