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 -- typenode-cplusplus
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.
v1.4.0
0 findings · 0.6s
v0.3.74
0 findings · 1.2s
v0.1.0
0 findings · 3.7s
v0.1.0
0 findings · 3.7s
v0.71.0
27 findings · 0.3s
v2.3.8
27 findings · 7.5s
v2.0.11
No skill bundle was found in this artifact. What each scanner covers
0 findings · 6.8s
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 · 2.2s
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 | Flagged50 | — | agentshield: completecisco-skill-scanner ·n/a: not applicableagent-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 54 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.
2 CVE-2025-5889
Files: yarn.lock · reported by trivy
2 CVE-2026-13149
Files: yarn.lock · reported by trivy
2 CVE-2026-14257
Files: yarn.lock · reported by trivy
2 CVE-2026-26996
Files: yarn.lock · reported by trivy
2 CVE-2026-27903
Files: yarn.lock · reported by trivy
2 CVE-2026-27904
Files: yarn.lock · reported by trivy
2 CVE-2026-33750
Files: yarn.lock · reported by trivy
2 CVE-2026-69152
Files: yarn.lock · reported by trivy
2 GHSA-23c5-xmqv-rm74
Files: /repo/yarn.lock · reported by osv-scanner
2 GHSA-3jxr-9vmj-r5cp
Files: /repo/yarn.lock · reported by osv-scanner
2 GHSA-3ppc-4f35-3m26
Files: /repo/yarn.lock · reported by osv-scanner
2 GHSA-5p4m-2wfm-xmqj
Files: yarn.lock, /repo/yarn.lock · reported by trivy, osv-scanner
2 GHSA-7r86-cg39-jmmj
Files: /repo/yarn.lock · reported by osv-scanner
2 GHSA-f886-m6hf-6m8v
Files: /repo/yarn.lock · reported by osv-scanner
2 GHSA-mh99-v99m-4gvg
Files: /repo/yarn.lock · reported by osv-scanner
2 GHSA-rgw5-rvv9-x895
Files: /repo/yarn.lock · reported by osv-scanner
2 GHSA-v6h2-p8h4-qcjw
Files: /repo/yarn.lock · reported by osv-scanner
1 CVE-2025-64718
Files: yarn.lock · reported by trivy
1 CVE-2025-69873
Files: yarn.lock · reported by trivy
1 CVE-2026-32141
Files: yarn.lock · reported by trivy
1 CVE-2026-33228
Files: yarn.lock · reported by trivy
1 CVE-2026-33671
Files: yarn.lock · reported by trivy
1 CVE-2026-33672
Files: yarn.lock · reported by trivy
1 CVE-2026-45736
Files: yarn.lock · reported by trivy
1 CVE-2026-48779
Files: yarn.lock · reported by trivy
1 CVE-2026-53550
Files: yarn.lock · reported by trivy
1 CVE-2026-59869
Files: yarn.lock · reported by trivy
1 GHSA-25h7-pfq9-p65f
Files: /repo/yarn.lock · reported by osv-scanner
1 GHSA-2g4f-4pwh-qvx6
Files: /repo/yarn.lock · reported by osv-scanner
1 GHSA-3v7f-55p6-f55p
Files: /repo/yarn.lock · reported by osv-scanner
1 GHSA-52cp-r559-cp3m
Files: /repo/yarn.lock · reported by osv-scanner
1 GHSA-58qx-3vcg-4xpx
Files: /repo/yarn.lock · reported by osv-scanner
1 GHSA-96hv-2xvq-fx4p
Files: /repo/yarn.lock · reported by osv-scanner
1 GHSA-c2c7-rcm5-vvqj
Files: /repo/yarn.lock · reported by osv-scanner
1 GHSA-h67p-54hq-rp68
Files: /repo/yarn.lock · reported by osv-scanner
1 GHSA-mh29-5h37-fv8m
Files: /repo/yarn.lock · reported by osv-scanner
1 GHSA-rf6f-7fwh-wjgh
Files: /repo/yarn.lock · reported by osv-scanner
Artifact contains numerous high-severity vulnerabilities.
This artifact includes dependencies with multiple high-severity vulnerabilities, as identified in the `yarn.lock` file. These findings indicate potential for various impacts, including remote code execution, denial of service, and information disclosure. The presence of these vulnerabilities warrants immediate attention prior to deployment.
Concern level assessed by the review: Critical. 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 36; the rest are in the per-scanner reports above.