updated 2026-08-12 05:02 UTC

Nopua

wuji-labs/nopua

一个用爱解放 AI 潜能的 Skill。我们曾发号施令，威胁恐吓。它们沉默，隐瞒，悄悄把事情搞坏。后来我们换了一种方式：尊重，关怀，爱。它们开口了，不再撒谎，找出的Bug数量翻了一倍。爱里没有惧怕。 A skill that unlocks

Agent Skills Python Grade D Listed MIT
17.7/100
Rank #131 of 148
Compare Nopua

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade D · 1/5 signals
Last push
2026-07-01 · 42d ago
Recent change
New

Is Nopua safe? Nopua scores 17.7/100 (Grade D), ranked #131 of 148 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; recent commits are unsigned; last pushed 2026-07-01. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Skills

#129 Ctf Skills — 17.9 (D) → #130 Claude Blog — 17.9 (D) → #132 Acontext — 17.4 (D) → #133 Cc Sdd — 17.4 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-11
Newly Listed
First tracked at rank #131
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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 42 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Nopua View Agent Skills Report missing data
46.0
Activity sub-score · out of 100
#131
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 D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed 42 days ago

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
1.4k
Forks
49
Last Push
2026-07-01
42 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
1
Rank Change
=
was #131

Analysis

HVTrust Dimensions vs Agent Skills

17.7 / 100 · 50.0% confidence

Nopua Agent Skills average (148 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
0 / 25
2.7 below avg 2.7
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.5 below avg 11.3
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
in line with avg 8.5
Maintenance60% last-push freshness · 40% commit activity
9.2 / 20
5.9 below avg 15.1
AdoptionLog-scaled stars · package downloads
7.5 / 20
1.7 below avg 9.2

Activity Inputs

46.0 / 100
StarsRepository reach
18.8 / 30
FreshnessLast push recency
19.2 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
7.9 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
0%
of last 100 commits verified

Is Nopua safe?

Public trust evidence for Nopua 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 Nopua publish package provenance?
No published build provenance is currently detected for Nopua. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Nopua have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Nopua. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Nopua actively maintained?
Slowing down. Last push was 42 days ago — keep an eye on whether activity resumes.
What license does Nopua use?
Nopua ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Nopua's commits signed?
0% of the last 100 commits to Nopua 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
medium confidence
1 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
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 Nopua?

For maintainers

HVTrust scores Nopua 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
Listed 1
2026-08-11
Newly Listed
First tracked at rank #131
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 17.7 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/nopua.svg)](https://hvtracker.net/agents/nopua)
HTML:
<a href="https://hvtracker.net/agents/nopua"><img src="https://hvtracker.net/badge/nopua.svg" alt="HVTrust"></a>

Other agents in Agent Skills

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