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.
6 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 -- hurdong/glance
6 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.
v2.0.11
22 findings · 16.5s
v0.3.74
6 findings · 7.0s
v0.1.0
1 finding · 10.1s
v0.1.0
1 finding · 10.1s
v0.71.0
88 findings · 0.9s
v2.3.8
195 findings · 12.2s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.4s
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 · 1.1s
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 | Flagged27 | — | agentshield ·n/a: not applicablecisco-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 313 findings across every scanner that examined this package. None of the 6 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.
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: AAK-GHA-IMMUTABLE-001 · Files: .github/workflows/deploy-frontend.yml · reported by agent-audit-kit
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.
12 DATA_EXFIL_JS_NETWORK
Files: /repo/frontend/src/components/auth/LoginPage.tsx, /repo/frontend/src/components/auth/LoginPopover.tsx, /repo/frontend/src/components/auth/SignupPage.tsx and 3 more · reported by cisco-skill-scanner
5 GHSA-3jxr-9vmj-r5cp
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
5 GHSA-f886-m6hf-6m8v
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
5 GHSA-mh99-v99m-4gvg
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
5 GHSA-rgw5-rvv9-x895
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-3v7f-55p6-f55p
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-42h9-826w-cgv3
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml, frontend/pnpm-lock.yaml and 1 more · reported by osv-scanner, trivy
4 GHSA-7q8q-rj6j-mhjq
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml, frontend/pnpm-lock.yaml and 1 more · reported by osv-scanner, trivy
4 GHSA-c2c7-rcm5-vvqj
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-jqh4-m9w3-8hp9
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml, /repo/frontend/pnpm-lock.yaml and 1 more · reported by trivy, osv-scanner
4 GHSA-mmx7-hfxf-jppx
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml, /repo/frontend/pnpm-lock.yaml and 1 more · reported by trivy, osv-scanner
4 GHSA-mwf2-3pr3-8698
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml, frontend/pnpm-lock.yaml and 1 more · reported by osv-scanner, trivy
4 GHSA-pmv8-rq9r-6j72
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml, frontend/pnpm-lock.yaml and 1 more · reported by osv-scanner, trivy
4 GHSA-qwww-vcr4-c8h2
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml, frontend/pnpm-lock.yaml and 1 more · reported by osv-scanner, trivy
4 GHSA-r4q5-vmmm-2653
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml, /repo/frontend/pnpm-lock.yaml and 1 more · reported by trivy, osv-scanner
3 GHSA-23c5-xmqv-rm74
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
3 GHSA-3ppc-4f35-3m26
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
3 GHSA-7r86-cg39-jmmj
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
3 LOW_ANALYZABILITY
Files: /repo/mobile, /repo, /repo/frontend · reported by cisco-skill-scanner
3 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/frontend/SKILL.md, /repo/mobile/SKILL.md · reported by cisco-skill-scanner
3 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/frontend/SKILL.md, /repo/mobile/SKILL.md · reported by cisco-skill-scanner
2 AAK-LEGAL-002
Files: frontend/package.json, mobile/package.json · reported by agent-audit-kit
2 CVE-2025-62718
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-12143
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-33244
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-33245
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-34077
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-40175
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-40181
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-42033
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-42034
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-42035
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-42036
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-42037
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-42038
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-42039
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-42040
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-42041
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-42042
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-42043
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-42044
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-42211
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-42264
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-42342
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-44486
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-44487
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-44488
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-44490
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-44494
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-44495
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-44496
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-53663
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-53666
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-53667
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-53669
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-54466
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-54490
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 CVE-2026-55685
Files: frontend/pnpm-lock.yaml, mobile/pnpm-lock.yaml · reported by trivy
2 GHSA-23hp-3jrh-7fpw
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-28wg-ghj8-5hjv
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-2j2x-hqr9-3h42
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-2v35-w6hq-6mfw
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-2v37-7h3g-55p8
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-337j-9hxr-rhxg
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-34x7-hfp2-rc4v
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-35jp-ww65-95wh
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3g43-6gmg-66jw
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3p68-rc4w-qgx5
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3w6x-2g7m-8v23
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-445q-vr5w-6q77
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-48c2-rrv3-qjmp
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-49rj-9fvp-4h2h
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-4w7w-66w2-5vf9
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-4x5r-pxfx-6jf8
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-52cp-r559-cp3m
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-5c9x-8gcm-mpgx
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-5p4m-2wfm-xmqj
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-62hf-57xw-28j9
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-67mh-4wv8-2f99
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-6chq-wfr3-2hj9
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-6g55-p6wh-862q
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-777c-7fjr-54vf
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-83g3-92jg-28cx
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-84g9-w2xq-vcv6
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-8646-j5j9-6r62
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-898c-q2cr-xwhg
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-8qq5-rm4j-mr97
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-8x6r-g9mw-2r78
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-8x88-c5mf-7j5w
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-9ppj-qmqm-q256
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-chx6-hx7r-mcp5
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-f22v-gfqf-p8f3
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-f6ww-3ggp-fr8h
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-fvcv-3m26-pcqx
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-fx2h-pf6j-xcff
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-fxqj-rqcc-2cmp
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-gvwx-54wh-qm9j
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-h67p-54hq-rp68
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-h8fp-f39c-q6mh
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-hfxv-24rg-xrqf
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-hmw2-7cc7-3qxx
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-j5f8-grm9-p9fc
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-j759-j44w-7fr8
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-m7pr-hjqh-92cm
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-mp7j-qc5w-4988
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-p92q-9vqr-4j8v
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-pf86-5x62-jrwf
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-pmwg-cvhr-8vh7
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-q8qp-cvcw-x6jj
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-qffp-2rhf-9h96
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-qx2v-qp2m-jg93
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-r28c-9q8g-f849
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-r292-9mhp-454m
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-r6q2-hw4h-h46w
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-rf6f-7fwh-wjgh
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-rxv8-25v2-qmq8
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-v6wh-96g9-6wx3
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-vf2m-468p-8v99
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-vmf3-w455-68vh
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-w8wr-v893-vjvp
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-w9j2-pvgh-6h63
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-wh4c-j3r5-mjhp
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-wrjc-x8rr-h8h6
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-x6wf-f3px-wcqx
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-xhjh-pmcv-23jw
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-xv26-6w52-cph6
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-xx6v-rp6x-q39c
Files: /repo/frontend/pnpm-lock.yaml, /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
1 AAK-SECRET-004
Files: backend/src/main/java/com/glance/domain/stocks/service/RedisStockService.java · reported by agent-audit-kit
1 AAK-SPLUNK-TOKLOG-001
Files: backend/src/main/java/com/glance/domain/stocks/service/MarketIndexService.java · reported by agent-audit-kit
1 EXCESSIVE_FILE_COUNT
Files: /repo/. · reported by cisco-skill-scanner
1 GHSA-25h7-pfq9-p65f
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2g4f-4pwh-qvx6
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-jxxr-4gwj-5jf2
Files: /repo/mobile/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mw96-cpmx-2vgc
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
1 opt.nerlo-rules.nerlo-install-run-bundled-artifact
Files: /repo/.cursor/rules/global.mdc · reported by nerlo-install-instruction
1 opt.nerlo-rules.nerlo-js-secret-to-network-egress
Files: /repo/frontend/src/components/auth/SignupPage.tsx · reported by nerlo-behavioral
Critical vulnerabilities and potential for secret exposure and network egress.
The artifact contains critical vulnerabilities in its frontend and mobile components, specifically within pnpm-lock.yaml files, which warrant immediate attention. A high-severity finding indicates potential for secrets to be exposed and sent over the network from frontend/src/components/auth/SignupPage.tsx. Additionally, the backend Java services include findings related to logging sensitive information and secrets in code. Multiple other high-severity vulnerabilities are present across various dependencies in both frontend and mobile components.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Showing 25 of 152; 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.