Waza
🥷 Engineering habits you already know, turned into skills AI assistants like Claude Code, Codex and Cursor can run.
Is Waza safe? Strong public trust posture, backed by multiple independent signals.
Compare Waza
How does it stack up against its Agent Skills neighbours?
Pick any agent to compare →In detail: Waza scores 77.7/100 (Grade B), ranked #20 of 385 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.0/10; 6% of recent commits are signed; no published advisory affects its latest release (@tw93/waza); last pushed 2026-10-15. Every point is earned from checkable signals — never paid placement. How scoring works →
How Waza 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.
- Raise the OSSF Scorecard from 4.0 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +9.6 → 87.3 A · #7 of 385
- Sign every commit6% signed today +4.7 → 82.4 A · #16 of 385
Chain of custody
Scanners check what the code says. This traces who ships Waza 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.
-
Source Partly signed
github.com/tw93/Waza, MIT, last pushed 2026-10-15. 6% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 4.0/10 (scanned Oct 15, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 0CI-Tests -1CII-Best-Practices 0Code-Review 0Contributors 6Dangerous-Workflow 10Dependency-Update-Tool 0Fuzzing 0License 10Maintained 10Packaging 10Pinned-Dependencies 0SAST 0Security-Policy 0Signed-Releases 0Token-Permissions 0Vulnerabilities 10 -
Published packages Linked and attested
- npm @tw93/waza Source link points back to this repo Build provenance attested
-
What you install today No known advisories
Latest release checked: @tw93/waza 3.40.0. No published advisory affects it (OSV, checked 2026-10-16).
Changes to this chain
- 2026-09-23 Package provenance attestation detected
- 2026-08-29 OSSF Scorecard: 4.0/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 Waza’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.
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 Waza compares in Agent Skills
- #18 Modlens 80.8 +3.1
- #19 Dsh Agent Teams 78.1 +0.4
- #20 Waza 77.7 this agent
- #21 Better Harness 77.4 −0.3
- #22 Claude Mem 77.0 −0.7
Bars show each HVTrust score; the tick marks Waza’s 77.7.
Where the 77.7 comes from
HVTrust dimensions vs the Agent Skills average
77.7 / 100 · 100.0% confidenceWaza Agent Skills average (385 agents)
Quick Trust Read
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
Activity & Reach
Analysis
Activity Inputs
83.4 / 100Common questions about Waza
Does Waza publish package provenance?
Does Waza have an OpenSSF Scorecard?
Is Waza actively maintained?
What license does Waza use?
Are Waza's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Waza'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.
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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/waza)
<a href="https://hvtracker.net/agents/waza"><img src="https://hvtracker.net/badge/waza.svg" alt="HVTrust"></a>
Other agents in Agent Skills
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON