Is Paperasse safe to use?

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

What is the trust score for Paperasse?

Paperasse scores 42.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 2.5k GitHub stars and is categorized under Agent Skills.

Paperasse

Repository

Website

🇫🇷 Skills pour agents IA spécialisés dans la bureaucratie française : Comptable, Notaire, ...

Agent Skills Python Listed MIT

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

OSSF Scorecard 2.9 / 10

Provenance None

Signed commits 36%

Last push 66d ago

Compare Paperasse

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Paperasse scores 42.7/100 (Grade D), ranked #320 of 371 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.9/10; 36% of recent commits are signed; last pushed 2026-08-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How Paperasse 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 2.9 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Dependency-Update-Tool 0 +12.7 → 55.4 C · #162 of 371
Sign every commit36% signed today +3.2 → 45.9 D · #293 of 371

Already done? Suggest a correction Add the trust badge

Chain of custody

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

Source Partly signed

github.com/romainsimon/paperasse, MIT, last pushed 2026-08-10. 36% 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 2.9/10 (scanned Oct 11, 2026). The checks that decide who can get a change released:
- Code Review4
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 3

CII-Best-Practices 0

Code-Review 4

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 3

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0
Published packages None

No registry package. Paperasse is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

2026-09-01 OSSF Scorecard: 3.5/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues Paperasse’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 Paperasse compares in Agent Skills

Bars show each HVTrust score; the tick marks Paperasse’s 42.7.

Where the 42.7 comes from

HVTrust dimensions vs the Agent Skills average

42.7 / 100 · 100.0% confidence

Paperasse Agent Skills average (371 agents)

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

5.4 / 25

2.6 below avg 8.0

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.6 below avg 11.4

Transparency50% declared license · 50% OSSF Scorecard

11.0 / 17

1.1 below avg 12.1

Maintenance60% last-push freshness · 40% commit activity

7.6 / 20

6.5 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-07

Rank Moved

Rank dropped 10 spots (#292 → #302)

2026-09-25

Rank Moved

Rank dropped 25 spots (#261 → #286)

2026-09-23

Rank Moved

Rank dropped 66 spots (#194 → #260)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 2.9/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 66 days ago. Fresh activity helps separate stable projects from stale ones.

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

47.1

Activity sub-score · out of 100

#320

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 C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-09-29 2026-10-15

Activity & Reach

Stars

2.5k

Forks

197

Last Push

2026-08-10

66 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼2

was #318

Analysis

Activity Inputs

47.1 / 100

StarsRepository reach

20.4 / 30

FreshnessLast push recency

15.8 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

10.7 / 20

Common questions about Paperasse

Public trust evidence for Paperasse 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 Paperasse publish package provenance?

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

Does Paperasse have an OpenSSF Scorecard?

Paperasse has an OpenSSF Scorecard score of 2.9/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 Paperasse actively maintained?

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

What license does Paperasse use?

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

Are Paperasse's commits signed?

35% of the last 100 commits to Paperasse 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

None detected

No MCP server signal detected.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

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

Tool / Plugin Surface

medium confidence

1 tags

Broad capability areas detected.

browser

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

Detailed evidence is not shown in the public view.

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

Maintain Paperasse?

For maintainers

HVTrust scores Paperasse 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-07

Rank Moved

Rank dropped 10 spots (#292 → #302)

2026-09-25

Rank Moved

Rank dropped 25 spots (#261 → #286)

2026-09-23

Rank Moved

Rank dropped 66 spots (#194 → #260)

2026-09-23

HVTrust Changed

HVTrust up 10.0pts (35.4 → 45.4)

2026-09-22

Newly Listed

First tracked at rank #194

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-09

Rank Moved

Rank dropped 13 spots (#212 → #225)

2026-09-05

Rank Moved

Rank dropped 12 spots (#187 → #199)

2026-09-01

Scorecard Added

OSSF Scorecard: 3.5/10

2026-09-01

Rank Moved

Rank rose 123 spots (#289 → #166)

2026-09-01

HVTrust Changed

HVTrust up 27.8pts (20.2 → 48.0)

2026-08-30

Rank Moved

Rank dropped 15 spots (#266 → #281)

2026-08-29

Rank Moved

Rank dropped 17 spots (#249 → #266)

2026-08-28

Rank Moved

Rank dropped 14 spots (#235 → #249)

2026-08-26

Newly Listed

First tracked at rank #228

GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Agent Skills

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

Paperasse

How Paperasse could raise its score

Chain of custody

Source Partly signed

Review and release Weak

Published packages None

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Paperasse compares in Agent Skills

Where the 42.7 comes from

HVTrust dimensions vs the Agent Skills average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Paperasse

AI agent surface

Maintain Paperasse?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in Agent Skills