Is Superpowers Zh safe to use?

Superpowers Zh has an HVTrust score of 63.9/100 (Grade C), ranked #72 of 384 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Superpowers Zh?

Superpowers Zh scores 63.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 8.5k GitHub stars and is categorized under Agent Skills.

Superpowers Zh

Repository Website

🦸 AI 编程超能力 · 中文增强版 — superpowers（250k+ ⭐）完整汉化 + 4 个中国原创 skills，让 Claude Code / Copilot CLI / Hermes Agent / Cursor / Windsurf / Kiro / Gemini CLI / Qoder 等 26 款 AI 编程工具真正会干活

Agent Skills JavaScript Listed MIT

Is Superpowers Zh safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.3 / 10

Provenance None

Signed commits 0%

Last push 15d ago

Advisories None known

Compare Superpowers Zh

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Superpowers Zh scores 63.9/100 (Grade C), ranked #72 of 384 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 4.3/10; recent commits are unsigned; no published advisory affects its latest release (superpowers-zh); last pushed 2026-10-26. Every point is earned from checkable signals — never paid placement. How scoring works →

How Superpowers Zh 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.

Publish build provenance for its packagesnpm publish --provenance from CI +14.7 → 78.6 B · #23 of 384
Raise the OSSF Scorecard from 4.3 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +9.7 → 73.6 B · #30 of 384
Sign every commit0% signed today +5.0 → 68.9 B · #38 of 384

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Superpowers Zh 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 Unsigned

github.com/jnMetaCode/superpowers-zh, MIT, last pushed 2026-10-26. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 4.3/10 (scanned Nov 5, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies6
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 6

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 10
Published packages Linked, not attested
- npm superpowers-zh 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: superpowers-zh 1.8.0. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

2026-09-01 OSSF Scorecard: 4.3/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 Superpowers Zh’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 Superpowers Zh compares in Agent Skills

Bars show each HVTrust score; the tick marks Superpowers Zh’s 63.9.

Where the 63.9 comes from

HVTrust dimensions vs the Agent Skills average

63.9 / 100 · 100.0% confidence

Superpowers Zh Agent Skills average (384 agents)

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

5.4 / 25

2.8 below avg 8.2

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.6 below avg 11.4

Transparency50% declared license · 50% OSSF Scorecard

12.2 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

16.8 / 20

2.8 above avg 14.0

AdoptionLog-scaled stars · package downloads

13.5 / 20

4.4 above avg 9.1

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-10-29

Grade Changed

Trust grade B → C

2026-10-28

Grade Changed

Trust grade C → B

2026-10-21

Grade Changed

Trust grade B → C

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.3/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.

Compare with another agent View Agent Skills Report missing data

78.4

Activity sub-score · out of 100

#72

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 C 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-11-10

Activity & Reach

Stars

8.5k

Forks

787

Last Push

2026-10-26

15 days ago

Commits (4 wk)

Downloads (7d)

1,073

npm

HN mentions (30d)

—

Open Issues

Rank Change

was #72

Analysis

Activity Inputs

78.4 / 100

StarsRepository reach

23.6 / 30

FreshnessLast push recency

22.9 / 25

ActivityRecent commits

18.2 / 25

CommunityFork signal

13.5 / 20

Common questions about Superpowers Zh

Superpowers Zh has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Superpowers Zh publish package provenance?

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

Does Superpowers Zh have an OpenSSF Scorecard?

Superpowers Zh has an OpenSSF Scorecard score of 4.3/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 Superpowers Zh actively maintained?

Maintained. Last push was 15 days ago.

What license does Superpowers Zh use?

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

Are Superpowers Zh's commits signed?

0% of the last 100 commits to Superpowers Zh 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

Superpowers Zh appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

2 detected

Public provider/service dependencies detected.

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 Superpowers Zh'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 dependencies: Anthropic, Google Gemini

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain Superpowers Zh?

For maintainers

HVTrust scores Superpowers Zh 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-29

Grade Changed

Trust grade B → C

2026-10-28

Grade Changed

Trust grade C → B

2026-10-21

Grade Changed

Trust grade B → C

2026-10-20

Grade Changed

Trust grade C → B

2026-10-07

Grade Changed

Trust grade B → C

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, Google Gemini

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 196 spots (#251 → #55)

2026-09-23

HVTrust Changed

HVTrust up 33.8pts (31.9 → 65.7)

2026-09-22

Newly Listed

First tracked at rank #251

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-05

Grade Changed

Trust grade D → B

2026-09-05

Rank Moved

Rank rose 177 spots (#209 → #32)

2026-09-05

HVTrust Changed

HVTrust up 23.8pts (43.9 → 67.7)

2026-09-03

Rank Moved

Rank dropped 10 spots (#195 → #205)

2026-09-02

Grade Changed

Trust grade B → D

2026-09-02

Rank Moved

Rank dropped 166 spots (#29 → #195)

2026-09-02

HVTrust Changed

HVTrust down 22.9pts (66.8 → 43.9)

2026-09-01

Scorecard Added

OSSF Scorecard: 4.3/10

2026-09-01

Grade Changed

Trust grade D → B

2026-09-01

Rank Moved

Rank rose 166 spots (#195 → #29)

2026-09-01

HVTrust Changed

HVTrust up 26.5pts (40.3 → 66.8)

2026-08-31

Rank Moved

Rank dropped 17 spots (#178 → #195)

2026-08-30

Rank Moved

Rank dropped 33 spots (#145 → #178)

2026-08-29

Rank Moved

Rank dropped 35 spots (#110 → #145)

2026-08-28

Rank Moved

Rank dropped 24 spots (#86 → #110)

2026-08-27

Rank Moved

Rank dropped 20 spots (#66 → #86)

2026-08-26

Rank Moved

Rank dropped 49 spots (#17 → #66)

GitHub → Website → npm: superpowers-zh

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/superpowers-zh.svg)](https://hvtracker.net/agents/superpowers-zh)
            
HTML:
            <a href="https://hvtracker.net/agents/superpowers-zh"><img src="https://hvtracker.net/badge/superpowers-zh.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

Superpowers Zh

How Superpowers Zh could raise its score

Chain of custody

Source Unsigned

Review and release Mixed

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 Superpowers Zh compares in Agent Skills

Where the 63.9 comes from

HVTrust dimensions vs the Agent Skills average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Superpowers Zh

AI agent surface

Maintain Superpowers Zh?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in Agent Skills