Loading the registry…
Document Editor monorepo
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.
2 critical findings reported by 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 -- document-editor
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.1s
v2.0.11
18 findings · 13.5s
v0.3.74
5 findings · 5.2s
v0.1.0
0 findings · 7.4s
v0.1.0
0 findings · 7.4s
v0.71.0
7 findings · 0.5s
v2.3.8
44 findings · 11.2s
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 · 2.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 | Flagged55 | — | 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 74 findings across every scanner that examined this package. None of the 2 findings rated critical by their scanner were dismissed.
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 DATA_EXFIL_JS_NETWORK
Files: /repo/client/src/api/documents.ts · reported by cisco-skill-scanner
3 AAK-LEGAL-002
Files: package.json, server/package.json, client/package.json · reported by agent-audit-kit
3 HIDDEN_DATA_FILE
Files: /repo/.env, /repo/server/.env · reported by cisco-skill-scanner
2 LOW_ANALYZABILITY
Files: /repo/server, /repo · reported by cisco-skill-scanner
2 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/server/SKILL.md · reported by cisco-skill-scanner
2 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/server/SKILL.md · reported by cisco-skill-scanner
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 CVE-2025-15284
Files: package-lock.json · reported by trivy
1 CVE-2025-66400
Files: package-lock.json · reported by trivy
1 CVE-2026-12590
Files: package-lock.json · reported by trivy
1 CVE-2026-2391
Files: package-lock.json · reported by trivy
1 CVE-2026-24001
Files: package-lock.json · reported by trivy
1 CVE-2026-4867
Files: package-lock.json · reported by trivy
1 CVE-2026-8723
Files: package-lock.json · reported by trivy
1 GHSA-23c5-xmqv-rm74
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-28wg-ghj8-5hjv
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-2qvq-rjwj-gvw9
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-2v37-7h3g-55p8
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-2w6w-674q-4c4q
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-37ch-88jc-xwx2
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3jxr-9vmj-r5cp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3mfm-83xf-c92r
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3ppc-4f35-3m26
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3v7f-55p6-f55p
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-442j-39wm-28r2
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4fh9-h7wg-q85m
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-4x5r-pxfx-6jf8
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-52cp-r559-cp3m
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-58qx-3vcg-4xpx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-5p4m-2wfm-xmqj
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-5xrq-8626-4rwp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-67mh-4wv8-2f99
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-6g55-p6wh-862q
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-6rw7-vpxm-498p
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-73rr-hh4g-fpgx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-7r86-cg39-jmmj
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-7rx3-28cr-v5wh
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-96hv-2xvq-fx4p
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-9cx6-37pm-9jff
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-c2c7-rcm5-vvqj
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-f886-m6hf-6m8v
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-fxqj-rqcc-2cmp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-h67p-54hq-rp68
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-hmw2-7cc7-3qxx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-mh29-5h37-fv8m
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-mh99-v99m-4gvg
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-mw96-cpmx-2vgc
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-q8mj-m7cp-5q26
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-qx2v-qp2m-jg93
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-r28c-9q8g-f849
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-rgw5-rvv9-x895
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v422-hmwv-36x6
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-w7fw-mjwx-w883
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xhpv-hc6g-r9c6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xjpj-3mr7-gcpf
Files: /repo/package-lock.json · reported by osv-scanner
Critical vulnerabilities found in artifact dependencies
This artifact contains critical vulnerabilities in its installed dependencies, identified by GHSA-5xrq-8626-4rwp and GHSA-2w6w-674q-4c4q, which warrant immediate attention. Additionally, numerous high-severity vulnerabilities are present in dependencies, and the artifact's own code exhibits low analyzability in multiple locations. The artifact also includes code capable of network egress, specifically JavaScript network data exfiltration, which is a medium-severity concern.
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 27; the rest are in the per-scanner reports above.