updated 2026-11-10 04:07 UTC

nWave

Repository Website

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.1 / 10
Provenance None
Signed commits 11%
Last push 3d ago
Advisories None known
Compare nWave

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →
Suggest a correction

In detail: nWave scores 55.7/100 (Grade C), ranked #168 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.1/10; 11% of recent commits are signed; no published advisory affects its latest release (nwave-ai); last pushed 2026-11-07. Every point is earned from checkable signals — never paid placement. How scoring works →

How nWave 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

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

  1. Source Partly signed

    github.com/nWave-ai/nWave, MIT, last pushed 2026-11-07. 11% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.1/10 (scanned Oct 25, 2026, refresh pending). The checks that decide who can get a change released:

    • Code Review1
    • Branch Protection0
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependenciesn/a
    All 18 Scorecard checks
    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 4
    Packaging -1
    Pinned-Dependencies -1
    SAST 0
    Security-Policy 0
    Signed-Releases 0
    Token-Permissions 10
    Vulnerabilities 10

  3. Published packages Linked, not attested

    • PyPI nwave-ai Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: nwave-ai 4.3.0. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

  • 2026-11-03 Package provenance attestation no longer detected
  • 2026-09-23 Package provenance attestation detected
  • 2026-08-31 OSSF Scorecard: 4.6/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 nWave’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 nWave compares in Agent Skills

  1. #166 Happy 55.8 +0.1
  2. #167 Naksha Studio 55.7 ±0
  3. #168 nWave 55.7 this agent
  4. #169 Video Shotcraft 55.7 ±0
  5. #170 drawio-skill 55.6 −0.1

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

Where the 55.7 comes from

HVTrust dimensions vs the Agent Skills average

55.7 / 100 · 100.0% confidence

nWave Agent Skills average (384 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.7 / 25
2.5 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.0 / 17
in line with avg 12.2
Maintenance60% last-push freshness · 40% commit activity
13.7 / 20
in line with avg 14.0
AdoptionLog-scaled stars · package downloads
11.1 / 20
2.0 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-11-06
Rank Moved
Rank rose 19 spots (#189 → #170)
2026-11-05
Provider Removed
Runtime surface shrank — no longer detected: Anthropic
2026-11-03
Provenance Removed
Package provenance attestation no longer detected
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.1/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
61.9
Activity sub-score · out of 100
#168
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 →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed 3 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
634
Forks
67
Last Push
2026-11-07
3 days ago
Commits (4 wk)
8?
Downloads (7d)
1,893
pypi
HN mentions (30d)
—
Open Issues
29
Rank Change
▼1
was #167

Analysis

Activity Inputs

61.9 / 100
StarsRepository reach
16.8 / 30
FreshnessLast push recency
24.6 / 25
ActivityRecent commits
11.9 / 25
CommunityFork signal
8.5 / 20

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?
No published build provenance is currently detected for nWave. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does nWave have an OpenSSF Scorecard?
nWave has an OpenSSF Scorecard score of 4.1/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?
Actively maintained. The repository was pushed to within the last 3 day(s).
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
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
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-11-05
Provider Removed
Runtime surface shrank — no longer detected: Anthropic
2026-11-03
Provenance Removed
Package provenance attestation no longer detected
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
Rank 14HVTrust 6Grade 3Score 2Scorecard 1Delisted 1Listed 1Provenance 1Surface 1Surface 1Provenance 1Surface 1
2026-11-06
Rank Moved
Rank rose 19 spots (#189 → #170)
2026-11-05
Provider Removed
Runtime surface shrank — no longer detected: Anthropic
2026-11-03
Provenance Removed
Package provenance attestation no longer detected
2026-11-03
Grade Changed
Trust grade B → C
2026-11-03
Rank Moved
Rank dropped 160 spots (#35 → #195)
2026-11-03
HVTrust Changed
HVTrust down 15.7pts (70.0 → 54.3)
2026-11-02
Rank Moved
Rank rose 19 spots (#54 → #35)
2026-11-02
HVTrust Changed
HVTrust up 4.3pts (65.7 → 70.0)
2026-11-02
Activity Score Changed
Activity score up 10pts (44 → 54)
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)
GitHub → Website → PyPI: nwave-ai

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 55.7 Grade C
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.4 · Raw JSON