How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Full methodology →
Signals refreshed2026-06-22 00:01 UTC·Repo last pushed 494 days ago — may be stale
Rank Trend
2026-06-202026-06-21
Activity & Reach
Stars
1.3k
Forks
188
Last Push
2025-02-13
494 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
13
Rank Change
=
was #242
Analysis
HVTrust Dimensions
29.5 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
9.5 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
11.7 / 17
MaintenanceFreshness and commits
0.0 / 20
AdoptionStars and downloads
7.5 / 20
Activity Inputs
29.4 / 100
StarsRepository reach
18.8 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
10.6 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
3.8 / 10
OpenSSF Scorecard · scanned Jun 21, 2026
Signed Commits
94%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection0
CI-Tests0
CII-Best-Practices0
Code-Review0
Contributors6
Dangerous-Workflow10
Dependency-Update-Tool0
Fuzzing0
License10
Maintained0
Packaging-1
Pinned-Dependencies2
SAST0
Security-Policy0
Signed-Releases0
Token-Permissions10
Vulnerabilities10
Is PyWinAssistant safe?
Public trust evidence for PyWinAssistant is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does PyWinAssistant publish package provenance?
No published build provenance is currently detected for PyWinAssistant. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does PyWinAssistant have an OpenSSF Scorecard?
PyWinAssistant has an OpenSSF Scorecard score of 3.8/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 PyWinAssistant actively maintained?
Stale. The repository has not been pushed to in 494 days. Consider whether the project is still being maintained.
What license does PyWinAssistant use?
PyWinAssistant ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are PyWinAssistant's commits signed?
94% of the last 100 commits to PyWinAssistant 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
high confidence
2 detected
Public provider/service dependencies detected.
Anthropic
OpenAI
Credential signal:
No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
browser
code
search
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 PyWinAssistant?
HVTrust scores PyWinAssistant 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
