Jscpd
Website
Copy/paste detector for source code. 220+ languages, Rust engine, SARIF/HTML/badge reporters, GitHub Action, MCP server for AI agents.
Is Jscpd safe? Promising trust profile, but some evidence still deserves review.
Compare Jscpd
How does it stack up against its Agent Skills neighbours?
Pick any agent to compare →In detail: Jscpd scores 66.1/100 (Grade B), ranked #52 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 7.4/10; 28% of recent commits are signed; last pushed 2026-10-10. Every point is earned from checkable signals — never paid placement. How scoring works →
How Jscpd 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.
- Sign every commit28% signed today +3.6 → 69.7 B · #34 of 371
- Raise the OSSF Scorecard from 7.4 to 9.0lowest checks: Code-Review 0, Signed-Releases 0, Branch-Protection 3 +3.3 → 69.4 B · #34 of 371
Chain of custody
Scanners check what the code says. This traces who ships Jscpd 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/kucherenko/jscpd, MIT, last pushed 2026-10-10. 28% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Strong
OpenSSF Scorecard rates the repository's practices 7.4/10 (scanned Oct 10, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection3
- Signed Releases0
- Dangerous Workflow10
- Token Permissions10
- Pinned Dependencies9
All 14 Scorecard checks
Binary-Artifacts 10Branch-Protection 3CII-Best-Practices 5Code-Review 0Dangerous-Workflow 10Fuzzing 10License 10Maintained 10Packaging 10Pinned-Dependencies 9SAST 10Security-Policy 10Signed-Releases 0Token-Permissions 10 -
Published packages None
No registry package. Jscpd is used from its repository, so what you run is whatever you check out: pin a release tag or commit.
Changes to this chain
No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Jscpd.
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 Jscpd’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.
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 Jscpd compares in Agent Skills
- #50 Openbrowser Ai 66.3 +0.2
- #51 Herdr 66.2 +0.1
- #52 Jscpd 66.1 this agent
- #53 Wshobson Agents 65.9 −0.2
- #54 Plannotator 65.4 −0.7
Bars show each HVTrust score; the tick marks Jscpd’s 66.1.
Where the 66.1 comes from
HVTrust dimensions vs the Agent Skills average
66.1 / 100 · 100.0% confidenceJscpd Agent Skills average (371 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B 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
Activity & Reach
Analysis
Activity Inputs
84.1 / 100Common questions about Jscpd
Does Jscpd publish package provenance?
Does Jscpd have an OpenSSF Scorecard?
Is Jscpd actively maintained?
What license does Jscpd use?
Are Jscpd's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Jscpd'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.
Maintain Jscpd?
For maintainers
HVTrust scores Jscpd 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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/jscpd)
<a href="https://hvtracker.net/agents/jscpd"><img src="https://hvtracker.net/badge/jscpd.svg" alt="HVTrust"></a>
Other agents in Agent Skills
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