Is PyWinAssistant safe to use?

PyWinAssistant has an HVTrust score of 29.2/100 (Grade D), ranked #415 of 468 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for PyWinAssistant?

PyWinAssistant scores 29.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 1.3k GitHub stars and is categorized under Browser & Computer Use.

PyWinAssistant

a-real-ai/pywinassistant

The first open-source Artificial Narrow Intelligence generalist agentic framework Computer-Using-Agent that fully operat

Browser & Computer Use Python Grade D Needs review MIT

29.2/100

Rank #415 of 468

Compare PyWinAssistant

How does it stack up against its Browser & Computer Use neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Needs review

Evidence coverage

Grade C · 2/5 signals

Last push

2025-02-13 · 539d ago

Recent change

No recent signal change

Is PyWinAssistant safe? PyWinAssistant scores 29.2/100 (Grade D), ranked #415 of 468 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.8/10; 94% of recent commits are signed; last pushed 2025-02-13. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Browser & Computer Use

#26 Nanobrowser — 34.3 (D) → #27 ScaleCUA — 29.6 (D) → #29 Open Operator — 28.3 (D) → #30 BrowserOS — 28.2 (D) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-07-29

Rank Moved

Rank dropped 11 spots (#405 → #416)

2026-07-15

Rank Moved

Rank dropped 24 spots (#375 → #399)

2026-07-14

Rank Moved

Rank dropped 21 spots (#354 → #375)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.8/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.

Refresh maintenance signals The repo was last pushed 539 days ago. Fresh activity helps separate stable projects from stale ones.

Review Flags

[4.2.1] no meaningful activity in 12 months (last push 2025-02-13)

Compare with another agent Get email alerts for PyWinAssistant View Browser & Computer Use Report missing data

29.4

Activity sub-score · out of 100

#28

In Browser & Computer Use

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. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-07-05 2026-08-06

Activity & Reach

Stars

1.3k

Forks

190

Last Push

2025-02-13

539 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #415

Analysis

HVTrust Dimensions vs Browser & Computer Use

29.2 / 100 · 100.0% confidence

PyWinAssistant Browser & Computer Use average (31 agents)

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

9.5 / 25

1.3 above avg 8.2

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.4 below avg 12.2

Transparency50% declared license · 50% OSSF Scorecard

11.7 / 17

in line with avg 11.3

Maintenance60% last-push freshness · 40% commit activity

0 / 20

11.3 below avg 11.3

AdoptionLog-scaled stars · package downloads

7.5 / 20

3.6 below avg 11.1

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 Aug 5, 2026

Signed Commits

94%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 0

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 2

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 10

Vulnerabilities 10

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 539 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

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

high confidence

1 detected

Public provider/service dependencies detected.

OpenAI

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

medium confidence

Declared

Declared plugin/integration surface detected.

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

How this surface has changed

Detected changes to PyWinAssistant'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-07-04

Provider Removed

Runtime surface shrank — no longer detected: Anthropic

Maintain PyWinAssistant?

For maintainers

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-07-29

Rank Moved

Rank dropped 11 spots (#405 → #416)

2026-07-15

Rank Moved

Rank dropped 24 spots (#375 → #399)

2026-07-14

Rank Moved

Rank dropped 21 spots (#354 → #375)

2026-07-13

Rank Moved

Rank dropped 36 spots (#318 → #354)

2026-07-04

Provider Removed

Runtime surface shrank — no longer detected: Anthropic

2026-06-30

HVTrust Changed

HVTrust up 4.7pts (24.8 → 29.5)

2026-06-29

HVTrust Changed

HVTrust down 4.7pts (29.5 → 24.8)

2026-06-24

Rank Moved

Rank dropped 35 spots (#275 → #310)

2026-06-23

Rank Moved

Rank dropped 23 spots (#252 → #275)

2026-06-22

Rank Moved

Rank dropped 10 spots (#242 → #252)

2026-06-21

Scorecard Added

OSSF Scorecard: 3.8/10

2026-06-21

Rank Moved

Rank rose 29 spots (#271 → #242)

2026-06-21

HVTrust Changed

HVTrust up 23.7pts (5.8 → 29.5)

2026-06-20

Newly Listed

First tracked at rank #271

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Browser & Computer Use

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 v4.2 · Raw JSON