Is nWave safe to use?

nWave has an HVTrust score of 36.9/100 (Grade D), ranked #20 of 148 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for nWave?

nWave scores 36.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 593 GitHub stars and is categorized under Agent Skills.

nWave

nWave-ai/nWave

AI agents that guide you from idea to working code, with you in control at every step.

Agent Skills Python Grade D Listed MIT

36.9/100

Rank #20 of 148

Compare nWave

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 C · 2/5 signals

Last push

2026-06-27 · 46d ago

Recent change

New

Is nWave safe? nWave scores 36.9/100 (Grade D), ranked #20 of 148 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; no OSSF Scorecard result yet; 11% of recent commits are signed; last pushed 2026-06-27. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Skills

#18 Skill Seekers — 37.8 (D) → #19 Nagisanzenin Engram — 37.2 (D) → #21 Ui Skills — 36.7 (D) → #22 Opensquilla — 36.6 (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 #20

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

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 46 days ago. Fresh activity helps separate stable projects from stale ones.

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

43.7

Activity sub-score · out of 100

#20

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-08-11 2026-08-12

Activity & Reach

Stars

593

Forks

Last Push

2026-06-27

46 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #20

Analysis

HVTrust Dimensions vs Agent Skills

36.9 / 100 · 67.0% confidence

nWave Agent Skills average (148 agents)

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

8.1 / 25

5.4 above avg 2.7

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

6.7 above 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

8.9 / 20

6.2 below avg 15.1

AdoptionLog-scaled stars · package downloads

6.7 / 20

2.5 below avg 9.2

Activity Inputs

43.7 / 100

StarsRepository reach

16.6 / 30

FreshnessLast push recency

18.6 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

8.3 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

—

Not available

Signed Commits

11%

of last 100 commits verified

Is nWave safe?

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

Yes. nWave's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does nWave have an OpenSSF Scorecard?

No OpenSSF Scorecard data is currently published for nWave. 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 nWave actively maintained?

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

What license does nWave use?

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

Are nWave's commits signed?

11% of the last 100 commits to nWave 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.

Anthropic

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

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

shell

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

Maintain nWave?

For maintainers

HVTrust scores nWave 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-08-11

Newly Listed

First tracked at rank #20

GitHub → PyPI: nwave-ai

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Agent Skills

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