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. Full methodology →
Signals refreshed2026-06-30 23:30 UTC·Repo last pushed yesterday
Activity & Reach
Stars
89
Forks
2
Last Push
2026-06-29
yesterday
Commits (4 wk)
94
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
1
Rank Change
NEW
Analysis
HVTrust Dimensions
65.5 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
14.8 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
15.4 / 17
MaintenanceFreshness and commits
19.8 / 20
AdoptionStars and downloads
4.7 / 20
Activity Inputs
63.5 / 100
StarsRepository reach
11.7 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
24.7 / 25
CommunityFork signal
2.2 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
8.1 / 10
OpenSSF Scorecard · scanned Jun 30, 2026
Signed Commits
93%
of last 100 commits verified
Security-Policy10
Maintained0
Code-Review9
Dangerous-Workflow10
Dependency-Update-Tool10
Packaging-1
Token-Permissions10
Binary-Artifacts10
Pinned-Dependencies10
CII-Best-Practices5
Signed-Releases10
Vulnerabilities9
SAST9
License10
Fuzzing0
Branch-Protection-1
Contributors3
CI-Tests9
Is DawnAI safe?
DawnAI 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 DawnAI publish package provenance?
No published build provenance is currently detected for DawnAI. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does DawnAI have an OpenSSF Scorecard?
DawnAI has an OpenSSF Scorecard score of 8.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 DawnAI actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does DawnAI use?
DawnAI ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are DawnAI's commits signed?
93% of the last 100 commits to DawnAI 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
Profile context only
HVTrust currently ranks supply-chain and project-integrity trust only. This public view shows a compact AI-agent surface snapshot from repo docs and manifests. These fields are descriptive context and do not affect the production HVTrust rank. An experimental local preview remains available in Score Lab →, and the policy boundary is tracked on the roadmap →
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.
OpenAI
Credential signal:
No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
code
filesystem
shell
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live
Maintain DawnAI?
HVTrust scores DawnAI 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.
Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v3.2 · Raw JSON
