Is Claude Paper safe to use?

Claude Paper has an HVTrust score of 45.2/100 (Grade D), ranked #297 of 371 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Claude Paper?

Claude Paper scores 45.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 344 GitHub stars and is categorized under Agent Skills.

Claude Paper

Repository

📖 Cross-agent research paper toolkit for Claude Code, Codex, OpenCode, and DeepSeek Harness—quick summaries, deep study materials, code demos, and a local web viewer.

Agent Skills Vue Listed MIT

Is Claude Paper safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 1.7 / 10

Provenance None

Signed commits 7%

Last push 59d ago

Advisories None known

Compare Claude Paper

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Claude Paper scores 45.2/100 (Grade D), ranked #297 of 371 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 1.7/10; 7% of recent commits are signed; no published advisory affects its latest release (@zlzliqing/claude-paper); last pushed 2026-08-14. Every point is earned from checkable signals — never paid placement. How scoring works →

How Claude Paper could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Raise the OSSF Scorecard from 1.7 to 9.0lowest checks: Branch-Protection 0, CI-Tests 0, CII-Best-Practices 0 +15.3 → 60.5 C · #96 of 371
Publish build provenance for its packagesnpm publish --provenance from CI +14.7 → 59.9 C · #102 of 371
Sign every commit7% signed today +4.6 → 49.8 D · #245 of 371

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Claude Paper and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities and, for skills, AST02 Supply Chain Compromise.

Source Partly signed

github.com/alaliqing/claude-paper, MIT, last pushed 2026-08-14. 7% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
Review and release Weak

OpenSSF Scorecard rates the repository's practices 1.7/10 (scanned Oct 10, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflown/a
- Token Permissionsn/a
- Pinned Dependenciesn/a
All 18 Scorecard checks

Binary-Artifacts 6

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 10

License 10

Maintained 0

Packaging -1

Pinned-Dependencies -1

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 0
Published packages Linked, not attested
- npm @zlzliqing/claude-paper Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
What you install today No known advisories

Latest release checked: @zlzliqing/claude-paper 1.2.1. No published advisory affects it (OSV, checked 2026-10-11).

Changes to this chain

2026-08-30 OSSF Scorecard: 2.8/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

GitHub repository data
Package downloads
Supply-chain checks
Public actions (missing)
Community mentions (missing)

Verify this score yourself

Every build re-issues Claude Paper’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read the skill’s instructions for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you install it, such as Cisco Skill Scanner.

How Claude Paper compares in Agent Skills

Bars show each HVTrust score; the tick marks Claude Paper’s 45.2.

Where the 45.2 comes from

HVTrust dimensions vs the Agent Skills average

45.2 / 100 · 100.0% confidence

Claude Paper Agent Skills average (371 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

2.5 / 25

5.4 below avg 7.9

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.6 below avg 11.4

Transparency50% declared license · 50% OSSF Scorecard

9.9 / 17

2.2 below avg 12.1

Maintenance60% last-push freshness · 40% commit activity

8.1 / 20

6.0 below avg 14.1

AdoptionLog-scaled stars · package downloads

8.2 / 20

0.8 below avg 9.0

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-10-09

Rank Moved

Rank dropped 16 spots (#271 → #287)

2026-09-25

Rank Moved

Rank dropped 23 spots (#241 → #264)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 1.7/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Refresh maintenance signals The repo was last pushed 59 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for Claude Paper View Agent Skills Report missing data

38.8

Activity sub-score · out of 100

#297

In Agent Skills

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-09-29 2026-10-12

Activity & Reach

Stars

344

Forks

Last Push

2026-08-14

59 days ago

Commits (4 wk)

Downloads (7d)

npm

HN mentions (30d)

—

Open Issues

Rank Change

was #297

Analysis

Activity Inputs

38.8 / 100

StarsRepository reach

15.2 / 30

FreshnessLast push recency

16.8 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

6.7 / 20

Common questions about Claude Paper

Public trust evidence for Claude Paper is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does Claude Paper publish package provenance?

No published build provenance is currently detected for Claude Paper. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Claude Paper have an OpenSSF Scorecard?

Claude Paper has an OpenSSF Scorecard score of 1.7/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Claude Paper actively maintained?

Slowing down. Last push was 59 days ago — keep an eye on whether activity resumes.

What license does Claude Paper use?

Claude Paper ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Claude Paper's commits signed?

6% of the last 100 commits to Claude Paper are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

medium confidence

Implemented

Claude Paper appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

medium confidence

1 detected

Public provider/service dependencies detected.

Anthropic

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to Claude Paper's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain Claude Paper?

For maintainers

HVTrust scores Claude Paper from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-10-09

Rank Moved

Rank dropped 16 spots (#271 → #287)

2026-09-25

Rank Moved

Rank dropped 23 spots (#241 → #264)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank rose 97 spots (#335 → #238)

2026-09-23

HVTrust Changed

HVTrust up 27.1pts (21.1 → 48.2)

2026-09-22

Newly Listed

First tracked at rank #335

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-15

Rank Moved

Rank dropped 10 spots (#222 → #232)

2026-09-13

Grade Changed

Trust grade C → D

2026-09-05

Rank Moved

Rank dropped 14 spots (#152 → #166)

2026-09-01

Rank Moved

Rank dropped 11 spots (#123 → #134)

2026-08-31

Rank Moved

Rank dropped 14 spots (#109 → #123)

2026-08-30

Scorecard Added

OSSF Scorecard: 2.8/10

2026-08-30

Grade Changed

Trust grade D → C

2026-08-30

Rank Moved

Rank rose 67 spots (#176 → #109)

2026-08-30

HVTrust Changed

HVTrust up 19.2pts (32.5 → 51.7)

2026-08-29

Rank Moved

Rank dropped 40 spots (#136 → #176)

2026-08-28

Rank Moved

Rank dropped 24 spots (#112 → #136)

2026-08-27

Rank Moved

Rank dropped 23 spots (#89 → #112)

2026-08-26

Newly Listed

First tracked at rank #89

GitHub → npm: @zlzliqing/claude-paper

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/claude-paper.svg)](https://hvtracker.net/agents/claude-paper)
            
HTML:
            <a href="https://hvtracker.net/agents/claude-paper"><img src="https://hvtracker.net/badge/claude-paper.svg" alt="HVTrust"></a>

Other agents in Agent Skills

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON

Claude Paper

How Claude Paper could raise its score

Chain of custody

Source Partly signed

Review and release Weak

Published packages Linked, not attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Claude Paper compares in Agent Skills

Where the 45.2 comes from

HVTrust dimensions vs the Agent Skills average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Claude Paper

AI agent surface

Maintain Claude Paper?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in Agent Skills