Loading the registry…
Implementation of the Cartan-Karlhede algorithm for determining the equivalence of spacetimes in general relativity
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.
4 critical findings reported by trivy, osv-scanner. The composite score alone does not reflect this — read the per-scanner reports below.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- cartan-karlhede
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
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.
v2.0.11
27 findings · 9.4s
v0.3.74
1 finding · 3.0s
v0.1.0
0 findings · 35.1s
v0.1.0
0 findings · 35.1s
v0.71.0
46 findings · 0.3s
v2.3.8
58 findings · 1.4s
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.1s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 1.9s
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 | Flagged49 | — | agentshield ·n/a: not applicablecisco-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 132 findings across every scanner that examined this package. None of the 4 findings rated critical by their scanner were dismissed.
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.
22 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: YARA_prompt_injection_unicode_steganography, FILE_MAGIC_MISMATCH, HIDDEN_DATA_FILE and 1 more · Files: /repo/docs/_build/html/_static/css/fonts/lato-normal-italic.woff2, /repo/docs/_build/html/_static/fonts/Lato/lato-italic.woff2, /repo/docs/_build/html/_sources/mathematics.rst.txt and 19 more · reported by cisco-skill-scanner
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/lean_action_ci.yml · reported by agent-audit-kit
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 GHSA-pw6j-qg29-8w7f
Files: /repo/uv.lock, uv.lock · reported by osv-scanner, trivy
1 CVE-2025-2148
Files: uv.lock · reported by trivy
1 CVE-2025-2149
Files: uv.lock · reported by trivy
1 CVE-2025-2953
Files: uv.lock · reported by trivy
1 CVE-2025-2998
Files: uv.lock · reported by trivy
1 CVE-2025-2999
Files: uv.lock · reported by trivy
1 CVE-2025-3000
Critical vulnerabilities found in dependencies.
The artifact includes dependencies with critical vulnerabilities, specifically PYSEC-2025-41, PYSEC-2024-259, PYSEC-2026-2120, and CVE-2025-32434, as identified in `uv.lock`. These issues could potentially lead to remote code execution or other severe impacts. Additionally, numerous high-severity vulnerabilities are present, which may enable further system compromise or data exposure.
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.
1 CVE-2025-3001
Files: uv.lock · reported by trivy
1 CVE-2025-30167
Files: uv.lock · reported by trivy
1 CVE-2025-32434
Files: uv.lock · reported by trivy
1 CVE-2025-3730
Files: uv.lock · reported by trivy
1 CVE-2025-47273
Files: uv.lock · reported by trivy
1 CVE-2025-47287
Files: uv.lock · reported by trivy
1 CVE-2025-66034
Files: uv.lock · reported by trivy
1 CVE-2025-67724
Files: uv.lock · reported by trivy
1 CVE-2025-67725
Files: uv.lock · reported by trivy
1 CVE-2025-67726
Files: uv.lock · reported by trivy
1 CVE-2025-68146
Files: uv.lock · reported by trivy
1 CVE-2025-71176
Files: uv.lock · reported by trivy
1 CVE-2026-22701
Files: uv.lock · reported by trivy
1 CVE-2026-25990
Files: uv.lock · reported by trivy
1 CVE-2026-31958
Files: uv.lock · reported by trivy
1 CVE-2026-32274
Files: uv.lock · reported by trivy
1 CVE-2026-35536
Files: uv.lock · reported by trivy
1 CVE-2026-40192
Files: uv.lock · reported by trivy
1 CVE-2026-42308
Files: uv.lock · reported by trivy
1 CVE-2026-42310
Files: uv.lock · reported by trivy
1 CVE-2026-42311
Files: uv.lock · reported by trivy
1 CVE-2026-4539
Files: uv.lock · reported by trivy
1 CVE-2026-49853
Files: uv.lock · reported by trivy
1 CVE-2026-49854
Files: uv.lock · reported by trivy
1 CVE-2026-49855
Files: uv.lock · reported by trivy
1 CVE-2026-54058
Files: uv.lock · reported by trivy
1 CVE-2026-54059
Files: uv.lock · reported by trivy
1 CVE-2026-54060
Files: uv.lock · reported by trivy
1 CVE-2026-55379
Files: uv.lock · reported by trivy
1 CVE-2026-55380
Files: uv.lock · reported by trivy
1 CVE-2026-55798
Files: uv.lock · reported by trivy
1 CVE-2026-59197
Files: uv.lock · reported by trivy
1 CVE-2026-59198
Files: uv.lock · reported by trivy
1 CVE-2026-59199
Files: uv.lock · reported by trivy
1 CVE-2026-59200
Files: uv.lock · reported by trivy
1 CVE-2026-59204
Files: uv.lock · reported by trivy
1 CVE-2026-59205
Files: uv.lock · reported by trivy
1 CVE-2026-59890
Files: uv.lock · reported by trivy
1 EXCESSIVE_FILE_COUNT
Files: /repo/. · reported by cisco-skill-scanner
1 GHSA-78cv-mqj4-43f7
Files: uv.lock · reported by trivy
1 GHSA-c678-jfcj-6jmf
Files: /repo/uv.lock · reported by osv-scanner
1 GHSA-f4hp-rmr7-r7v8
Files: /repo/uv.lock · reported by osv-scanner
1 GHSA-qfhq-4f3w-5fph
Files: /repo/uv.lock · reported by osv-scanner
1 GHSA-rrmf-rvhw-rf47
Files: /repo/uv.lock · reported by osv-scanner
1 GHSA-vgrw-7cvw-pwgx
Files: /repo/uv.lock · reported by osv-scanner
1 GHSA-x3gm-94wq-g975
Files: /repo/uv.lock · reported by osv-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
1 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 PYSEC-2024-259
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-191
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-198
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-203
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-204
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-205
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-206
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-207
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-208
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-209
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-265
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-266
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-267
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-41
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-49
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1374
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1375
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1389
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-139
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-140
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1477
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-165
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1845
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1970
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1974
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2120
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2121
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2132
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2249
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2250
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2252
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2253
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2254
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2255
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2256
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2257
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2286
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2287
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2874
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2987
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3387
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3388
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3389
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3447
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3451
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3453
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3454
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3493
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3494
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3495
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3496
Files: /repo/uv.lock · reported by osv-scanner
1 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 UNANALYZABLE_BINARY
Files: /repo/papers/2007.04123.pdf · reported by cisco-skill-scanner
Showing 25 of 59; the rest are in the per-scanner reports above.