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 -- hrms-frontend
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.0s
v2.0.11
4 findings · 8.7s
v0.3.74
4 findings · 2.7s
v0.1.0
0 findings · 4.5s
v0.1.0
0 findings · 4.5s
v0.71.0
14 findings · 0.3s
v2.3.8
102 findings · 6.9s
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.6s
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 | Flagged54 | — | 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 124 findings across every scanner that examined this package.
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.
4 GHSA-23c5-xmqv-rm74
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-3jxr-9vmj-r5cp
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-3ppc-4f35-3m26
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-7r86-cg39-jmmj
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-f886-m6hf-6m8v
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-mh99-v99m-4gvg
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-rgw5-rvv9-x895
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-v6h2-p8h4-qcjw
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 CVE-2025-27789
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-27121
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-27122
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-27125
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-27901
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-42573
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-42599
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 GHSA-28wg-ghj8-5hjv
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-2v37-7h3g-55p8
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-33hq-fvwr-56pm
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3v7f-55p6-f55p
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-48c2-rrv3-qjmp
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-5j98-mcp5-4vw2
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-67mh-4wv8-2f99
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-6g55-p6wh-862q
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-8qm3-746x-r74r
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-968p-4wvh-cqc8
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-c2c7-rcm5-vvqj
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-cfw5-2vxh-hr84
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-crpf-4hrx-3jrp
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-f7gr-6p89-r883
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-fxqj-rqcc-2cmp
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-g2pg-6438-jwpf
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-m56q-vw4c-c2cp
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-mw96-cpmx-2vgc
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-mwv9-gp5h-frr4
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-phwv-c562-gvmh
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-pr6f-5x2q-rwfp
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-pxg6-pf52-xh8x
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-qx2v-qp2m-jg93
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-r28c-9q8g-f849
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-rcqx-6q8c-2c42
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-vj54-72f3-p5jv
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
1 AAK-LEGAL-002
Files: package.json · reported by agent-audit-kit
1 AAK-OAUTH-008
Files: api-doc.json · reported by agent-audit-kit
1 AAK-SECRET-006
Files: .env · reported by agent-audit-kit
1 AAK-SUPPLY-005
Files: package-lock.json · reported by agent-audit-kit
1 GHSA-29g2-3rmr-qm68
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-2crg-3p73-43xp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-356w-63v5-8wf4
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3f6h-2hrp-w5wx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4r4m-qw57-chr8
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4w7w-66w2-5vf9
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-6q87-84jw-cjhp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-859w-5945-r5v3
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-866w-xmhq-wj7x
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-93m4-6634-74q7
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-fx2h-pf6j-xcff
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-g4jq-h2w9-997c
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-jqfw-vq24-v9c3
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v6wh-96g9-6wx3
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-vg6x-rcgg-rjx6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-wqjv-9729-c5q2
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-x574-m823-4x7w
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xcj6-pq6g-qj4x
Files: /repo/package-lock.json · reported by osv-scanner
1 HIDDEN_DATA_FILE
Files: /repo/.env · 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
Artifact contains numerous high-severity vulnerabilities in dependencies.
The artifact includes dependencies with multiple high-severity vulnerabilities, as identified by OSV-scanner. These issues are present in `package-lock.json` and `pnpm-lock.yaml`, indicating widespread dependency concerns. Additionally, a high-severity LOW_ANALYZABILITY finding from cisco-skill-scanner for the `/repo` suggests potential issues with code clarity or complexity that could mask further risks. These findings collectively point to significant security risks within the installed code.
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.
Showing 25 of 45; the rest are in the per-scanner reports above.