Is nWave safe to use?

nWave has an HVTrust score of 70.7/100 (Grade B), ranked #31 of 351 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 70.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 616 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 Listed MIT

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

OSSF Scorecard 4.3 / 10

Provenance Attested

Signed commits 11%

Last push 10d ago

Compare nWave

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Suggest a correction

In detail: nWave scores 70.7/100 (Grade B), ranked #31 of 351 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 4.3/10; 11% of recent commits are signed; last pushed 2026-09-16. Every point is earned from checkable signals — never paid placement. How scoring works →

How nWave compares in Agent Skills

Bars show each HVTrust score; the tick marks nWave’s 70.7.

Where the 70.7 comes from

HVTrust dimensions vs the Agent Skills average

70.7 / 100 · 100.0% confidence

nWave Agent Skills average (351 agents)

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

13.4 / 25

5.3 above avg 8.1

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

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

14.1 / 20

in line with avg 14.2

AdoptionLog-scaled stars · package downloads

9.6 / 20

0.6 above avg 9.0

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Provenance Added

Package provenance attestation detected

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.3/10. Tighten the weakest checks to improve public safety evidence.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

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

57.6

Activity sub-score · out of 100

#31

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 B 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-08-11 2026-09-26

Activity & Reach

Stars

616

Forks

Last Push

2026-09-16

10 days ago

Commits (4 wk)

Downloads (7d)

147

pypi

HN mentions (30d)

—

Open Issues

Rank Change

was #31

Analysis

Activity Inputs

57.6 / 100

StarsRepository reach

16.7 / 30

FreshnessLast push recency

23.6 / 25

ActivityRecent commits

8.7 / 25

CommunityFork signal

8.4 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

4.3 / 10

OpenSSF Scorecard · scanned Sep 16, 2026

Signed Commits

11%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 1

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 7

Packaging -1

Pinned-Dependencies -1

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 10

Vulnerabilities 10

Common questions about nWave

nWave 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 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?

nWave 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 nWave actively maintained?

Maintained. Last push was 10 days ago.

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

How this surface has changed

Detected changes to nWave'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 dependency: Anthropic

2026-09-23

Provenance Added

Package provenance attestation detected

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-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 258 spots (#289 → #31)

2026-09-23

HVTrust Changed

HVTrust up 42.4pts (27.5 → 69.9)

2026-09-22

Newly Listed

First tracked at rank #289

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-06

Grade Changed

Trust grade D → B

2026-09-06

Rank Moved

Rank rose 184 spots (#210 → #26)

2026-09-06

HVTrust Changed

HVTrust up 25.4pts (45.9 → 71.3)

2026-09-05

Rank Moved

Rank dropped 11 spots (#199 → #210)

2026-09-03

Rank Moved

Rank dropped 11 spots (#181 → #192)

2026-09-01

Rank Moved

Rank dropped 15 spots (#157 → #172)

2026-08-31

Scorecard Added

OSSF Scorecard: 4.6/10

2026-08-31

Rank Moved

Rank rose 18 spots (#175 → #157)

2026-08-31

HVTrust Changed

HVTrust up 6.4pts (40.5 → 46.9)

2026-08-30

Rank Moved

Rank dropped 28 spots (#147 → #175)

2026-08-29

Rank Moved

Rank dropped 34 spots (#113 → #147)

2026-08-28

Rank Moved

Rank dropped 24 spots (#89 → #113)

2026-08-27

Rank Moved

Rank dropped 20 spots (#69 → #89)

2026-08-26

Rank Moved

Rank dropped 49 spots (#20 → #69)

2026-08-25

HVTrust Changed

HVTrust up 3.4pts (36.3 → 39.7)

2026-08-25

Activity Score Changed

Activity score up 12pts (42 → 54)

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) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON