Loading the registry…
A headless library for research paper management
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.
1 critical finding 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 -- libpaper
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
6 findings · 7.9s
v0.3.74
0 findings · 2.5s
v0.1.0
0 findings · 3.3s
v0.1.0
0 findings · 3.3s
v0.71.0
71 findings · 0.3s
v2.3.8
73 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 19, 2026 | Flagged50 | — | 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 150 findings across every scanner that examined this package. None of the 1 finding 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.
4 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: /repo/docs/docs/SKILL.md, /repo/docs/docs/api/SKILL.md · reported by cisco-skill-scanner
The model could have called any of these a false positive and did not.
2 GHSA-jm82-fx9c-mx94
Files: /repo/uv.lock, uv.lock · reported by osv-scanner, trivy
1 CVE-2025-50181
Files: uv.lock · reported by trivy
1 CVE-2025-50182
Files: uv.lock · reported by trivy
1 CVE-2025-54121
Files: uv.lock · reported by trivy
1 CVE-2025-55197
Files: uv.lock · reported by trivy
1 CVE-2025-62707
Files: uv.lock · reported by trivy
1 CVE-2025-62708
Files: uv.lock · reported by trivy
1 CVE-2025-62727
Files: uv.lock · reported by trivy
1 CVE-2025-66019
Files: uv.lock · reported by trivy
1 CVE-2025-66418
Files: uv.lock · reported by trivy
1 CVE-2025-66471
Files: uv.lock · reported by trivy
1 CVE-2025-68142
Files: uv.lock · reported by trivy
1 CVE-2025-68146
Files: uv.lock · reported by trivy
1 CVE-2025-69534
Files: uv.lock · reported by trivy
1 CVE-2025-71176
Files: uv.lock · reported by trivy
1 CVE-2026-21441
Files: uv.lock · reported by trivy
1 CVE-2026-22690
Files: uv.lock · reported by trivy
1 CVE-2026-22691
Files: uv.lock · reported by trivy
1 CVE-2026-22701
Files: uv.lock · reported by trivy
1 CVE-2026-22702
Files: uv.lock · reported by trivy
1 CVE-2026-24486
Files: uv.lock · reported by trivy
1 CVE-2026-24688
Files: uv.lock · reported by trivy
1 CVE-2026-25645
Files: uv.lock · reported by trivy
1 CVE-2026-27024
Files: uv.lock · reported by trivy
1 CVE-2026-27025
Files: uv.lock · reported by trivy
1 CVE-2026-27026
Files: uv.lock · reported by trivy
1 CVE-2026-27628
Files: uv.lock · reported by trivy
1 CVE-2026-27888
Files: uv.lock · reported by trivy
1 CVE-2026-28351
Files: uv.lock · reported by trivy
1 CVE-2026-28684
Files: uv.lock · reported by trivy
1 CVE-2026-28804
Files: uv.lock · reported by trivy
1 CVE-2026-31826
Files: uv.lock · reported by trivy
1 CVE-2026-32274
Files: uv.lock · reported by trivy
1 CVE-2026-33123
Files: uv.lock · reported by trivy
1 CVE-2026-33699
Files: uv.lock · reported by trivy
1 CVE-2026-40260
Files: uv.lock · reported by trivy
1 CVE-2026-40347
Files: uv.lock · reported by trivy
1 CVE-2026-41168
Files: uv.lock · reported by trivy
1 CVE-2026-41312
Files: uv.lock · reported by trivy
1 CVE-2026-41313
Files: uv.lock · reported by trivy
1 CVE-2026-41314
Files: uv.lock · reported by trivy
1 CVE-2026-42561
Files: uv.lock · reported by trivy
1 CVE-2026-44431
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-46338
Files: uv.lock · reported by trivy
1 CVE-2026-48155
Files: uv.lock · reported by trivy
1 CVE-2026-48156
Files: uv.lock · reported by trivy
1 CVE-2026-48710
Files: uv.lock · reported by trivy
1 CVE-2026-48735
Files: uv.lock · reported by trivy
1 CVE-2026-48817
Files: uv.lock · reported by trivy
1 CVE-2026-48818
Files: uv.lock · reported by trivy
1 CVE-2026-49460
Files: uv.lock · reported by trivy
1 CVE-2026-49461
Files: uv.lock · reported by trivy
1 CVE-2026-53537
Files: uv.lock · reported by trivy
1 CVE-2026-53538
Files: uv.lock · reported by trivy
1 CVE-2026-53539
Files: uv.lock · reported by trivy
1 CVE-2026-53540
Files: uv.lock · reported by trivy
1 CVE-2026-54282
Files: uv.lock · reported by trivy
1 CVE-2026-54283
Files: uv.lock · reported by trivy
1 CVE-2026-54530
Files: uv.lock · reported by trivy
1 CVE-2026-54531
Files: uv.lock · reported by trivy
1 CVE-2026-54651
Files: uv.lock · reported by trivy
1 CVE-2026-59935
Files: uv.lock · reported by trivy
1 CVE-2026-59936
Files: uv.lock · reported by trivy
1 CVE-2026-59937
Files: uv.lock · reported by trivy
1 CVE-2026-59938
Files: uv.lock · reported by trivy
1 CVE-2026-61632
Files: uv.lock · reported by trivy
1 CVE-2026-67422
Files: uv.lock · reported by trivy
1 CVE-2026-71852
Files: uv.lock · reported by trivy
1 CVE-2026-71870
Files: uv.lock · reported by trivy
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-141
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-161
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1825
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1827
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1828
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1829
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1830
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1831
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1832
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1833
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1845
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1852
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1941
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1942
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1996
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1997
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1998
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1999
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2009
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-215
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2270
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2275
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2280
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2281
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-248
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-249
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2987
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2999
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3004
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3005
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3006
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3007
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3009
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3010
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3011
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3012
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3013
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3014
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3015
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3016
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3017
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3018
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3019
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3020
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3021
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3022
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3023
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3024
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3025
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3026
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3027
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3036
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3037
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3038
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3039
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3040
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3041
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3609
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3610
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3611
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3612
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3613
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3654
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3655
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3656
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-89
Files: /repo/uv.lock · reported by osv-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
1 The model did not answer for these findings.
Rules: PYSEC-2026-1994 · Files: /repo/uv.lock · reported by osv-scanner
Critical dependency vulnerability and API data handling risks.
A critical vulnerability (PYSEC-2026-2120) exists in a dependency listed in `uv.lock`. Multiple high-severity vulnerabilities are present in other dependencies. High-severity findings from the `bearer` scanner indicate potential risks in API data handling within `/repo/src/libpaper/api/routers/papers.py` and in the PDF extraction process in `/repo/src/libpaper/extractors/pdf_extractor.py`. These findings may relate to insecure data processing, sensitive information exposure, or file system interactions.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Showing 21 of 21; the rest are in the per-scanner reports above.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.