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 -- chemxploreml
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
2 findings · 0.6s
v2.0.11
22 findings · 8.3s
v0.3.74
2 findings · 5.8s
v0.1.0
0 findings · 3.6s
v0.1.0
0 findings · 3.6s
v0.71.0
0 findings · 0.3s
v2.3.8
20 findings · 6.9s
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 · 1.0s
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 | Flagged69 | — | 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 46 findings across every scanner that examined this package.
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.
3 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, permissions-no-block, hooks-no-pretooluse · Files: .github/workflows/deploy.yml, .vscode/settings.json · reported by agent-audit-kit, agentshield
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.
8 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/ml-training/SKILL.md, /repo/molecular-analysis/SKILL.md and 5 more · reported by cisco-skill-scanner
8 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/ml-training/SKILL.md, /repo/molecular-analysis/SKILL.md and 5 more · reported by cisco-skill-scanner
5 YARA_prompt_injection_unicode_steganography
Files: /repo/public/screenshots/load-file/cxml-load-file-analysis-plots-0.png, /repo/public/screenshots/settings/cxml-settings-configurations.png, /repo/public/screenshots/vectorize-molecules/cxml-vectorize-molecules.png · reported by cisco-skill-scanner
1 AAK-LEGAL-002
Files: package.json · reported by agent-audit-kit
1 FILE_MAGIC_MISMATCH
Files: /repo/.vitepress/theme/index.ts · reported by cisco-skill-scanner
1 GHSA-28wg-ghj8-5hjv
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1
Multiple high-severity vulnerabilities in dependencies
The artifact contains multiple high-severity vulnerabilities in its dependencies, as identified by osv-scanner. These issues are present in the pnpm-lock.yaml file, indicating potential risks within the installed code. These vulnerabilities could lead to various impacts depending on the specific dependency and its usage.
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.
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-356w-63v5-8wf4
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4fh9-h7wg-q85m
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4r4m-qw57-chr8
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-67mh-4wv8-2f99
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-859w-5945-r5v3
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-93m4-6634-74q7
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-fxqj-rqcc-2cmp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-g4jq-h2w9-997c
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-jqfw-vq24-v9c3
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-qx2v-qp2m-jg93
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-v6wh-96g9-6wx3
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-x574-m823-4x7w
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-xcj6-pq6g-qj4x
Files: /repo/pnpm-lock.yaml · reported by osv-scanner