Loading the registry…
YAPI TypeScript API Generator
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.
npm: yapi-ts-gen @ 1.0.13, 0 findings
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 -- yapi-ts-gen
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.5s
v2.0.11
8 findings · 6.6s
v0.3.74
1 finding · 0.8s
v0.1.0
0 findings · 2.8s
v0.1.0
0 findings · 2.8s
v0.1.0
0 findings · 7.1s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.71.0
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.2s
v2.3.8
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.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 20, 2026 | Flagged85 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source: completetrivy ·n/a: not applicableosv-scanner ·n/a: not applicabletrivy_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 9 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 2 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
The model could have called any of these a false positive and did not.
4 DATA_EXFIL_JS_FS_ACCESS
Files: /repo/src/cli.ts, /repo/src/fetcher.ts, /repo/src/generator.ts and 1 more · reported by cisco-skill-scanner
1 AAK-SUPPLY-004
Files: package.json · reported by agent-audit-kit
1 DATA_EXFIL_JS_NETWORK
Files: /repo/src/fetcher.ts · reported by cisco-skill-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
2 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: /repo/SKILL.md · reported by cisco-skill-scanner
High severity findings, including file system access and network egress.
The artifact contains high severity findings, notably potential file system access in `cli.ts`, `fetcher.ts`, `generator.ts`, and `utils.ts`. Additional high severity issues are present in `fetcher.ts`, `generator.ts`, and `utils.ts`. A high severity `LOW_ANALYZABILITY` finding suggests difficulty in fully assessing the code. Medium severity findings also indicate network egress capabilities.
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.