Loading the registry…
A CLI tool for translating Xcode string catalogs.
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.
7 critical findings reported by trivy, osv-scanner. The composite score alone does not reflect this — read the per-scanner reports below.
pypi: string-catalog @ 0.6.0, 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 -- string-catalog
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.
v2.0.11
3 findings · 9.2s
v0.3.74
1 finding · 1.8s
v0.1.0
0 findings · 3.9s
v0.1.0
0 findings · 3.9s
v0.1.0
0 findings · 9.5s
v0.71.0
32 findings · 0.3s
v2.3.8
33 findings · 2.0s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
vv0.3.2
No Go packages were 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 | Flagged49 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source: completetrivy: 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 69 findings across every scanner that examined this package. None of the 7 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 3 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
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.
1 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 · Files: .github/workflows/publish.yml · reported by agent-audit-kit
The model could have called any of these a false positive and did not.
2 CVE-2025-59420
Files: uv.lock · reported by trivy
2 CVE-2025-61920
Files: uv.lock · reported by trivy
2 CVE-2025-62706
Files: uv.lock · reported by trivy
2 CVE-2025-68158
Files: uv.lock · reported by trivy
2 CVE-2026-27962
Files: uv.lock · reported by trivy
2 CVE-2026-28490
Files: uv.lock · reported by trivy
2 CVE-2026-28498
Files: uv.lock · reported by trivy
2 CVE-2026-41425
Files:
3 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: TOOL_ABUSE_UNDECLARED_NETWORK, SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: /repo/repo/README.md, /repo/SKILL.md · reported by cisco-skill-scanner
Critical vulnerabilities and high-risk code patterns detected
The artifact contains multiple critical vulnerabilities in its dependencies, identified by trivy and osv-scanner in uv.lock. High-severity findings from bearer indicate potential sensitive data exposure or insecure operations within appstoreconnect_cli.py, utils.py, whats_new.py, and xcstrings_cli.py. Additionally, a medium-severity finding from cisco-skill-scanner points to undeclared network egress.
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.
2 CVE-2026-41479
Files: uv.lock · reported by trivy
2 CVE-2026-44681
Files: uv.lock · reported by trivy
2 GHSA-537c-gmf6-5ccf
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
2 PYSEC-2026-1200
Files: /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-1201
Files: /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-1202
Files: /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-1203
Files: /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-188
Files: /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2116
Files: /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2117
Files: /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-2119
Files: /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-25
Files: /repo/uv.lock · reported by osv-scanner
2 PYSEC-2026-287
Files: /repo/uv.lock · reported by osv-scanner
1 CVE-2025-43859
Files: uv.lock · reported by trivy
1 CVE-2025-69872
Files: uv.lock · reported by trivy
1 CVE-2025-71176
Files: uv.lock · reported by trivy
1 CVE-2026-26007
Files: uv.lock · reported by trivy
1 CVE-2026-34073
Files: uv.lock · reported by trivy
1 CVE-2026-39892
Files: uv.lock · reported by trivy
1 CVE-2026-4539
Files: uv.lock · reported by trivy
1 CVE-2026-45409
Files: uv.lock · reported by trivy
1 CVE-2026-69247
Files: uv.lock · reported by trivy
1 CVE-2026-69248
Files: uv.lock · reported by trivy
1 CVE-2026-69249
Files: uv.lock · reported by trivy
1 PYSEC-2026-1845
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2132
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2141
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-215
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2447
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2987
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-348
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-35
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3552
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3553
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3554
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-36
Files: /repo/uv.lock · reported by osv-scanner
Showing 15 of 15; the rest are in the per-scanner reports above.