Waza has an HVTrust score of 68.9/100 (Grade B), ranked #4 of 148 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Waza?

Waza scores 68.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 6.8k GitHub stars and is categorized under Agent Skills.

Waza

tw93/Waza

🥷 Engineering habits you already know, turned into skills Claude can run.

Agent Skills Python Grade B Listed MIT

68.9/100

Rank #4 of 148

Compare Waza

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-09 · 3d ago

Recent change

New

Is Waza safe? Waza scores 68.9/100 (Grade B), ranked #4 of 148 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; no OSSF Scorecard result yet; 5% of recent commits are signed; last pushed 2026-08-09. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Skills

#2 Cc Safety Net — 74.5 (B) → #3 Better Harness — 70.6 (B) → #5 Dev Browser — 65.3 (B) → #6 Pg Aiguide — 62.4 (C) →

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 #4

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.

Compare with Larksuite Cli Get email alerts for Waza View Agent Skills Report missing data

80.8

Activity sub-score · out of 100

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

Activity & Reach

Stars

6.8k

Forks

403

Last Push

2026-08-09

3 days ago

Commits (4 wk)

Downloads (7d)

265

npm

HN mentions (30d)

—

Open Issues

Rank Change

was #4

Analysis

HVTrust Dimensions vs Agent Skills

68.9 / 100 · 100.0% confidence

Waza Agent Skills average (148 agents)

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

7.8 / 25

5.1 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

18.5 / 20

3.4 above avg 15.1

AdoptionLog-scaled stars · package downloads

12.4 / 20

3.2 above avg 9.2

Activity Inputs

80.8 / 100

StarsRepository reach

23.0 / 30

FreshnessLast push recency

24.6 / 25

ActivityRecent commits

21.0 / 25

CommunityFork signal

12.1 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

—

Not available

Signed Commits

of last 100 commits verified

Is Waza safe?

Waza 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 Waza publish package provenance?

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

Does Waza have an OpenSSF Scorecard?

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

Actively maintained. The repository was pushed to within the last 3 day(s).

What license does Waza use?

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

Are Waza's commits signed?

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

Compare Waza head-to-head

Waza vs Larksuite Cli → Waza vs Cc Safety Net → Waza vs Better Harness →

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

None detected

No clear third-party provider dependency 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

Maintain Waza?

For maintainers

HVTrust scores Waza 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 #4

GitHub → npm: @tw93/waza

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Agent Skills

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