updated 2026-11-05 12:09 UTC

PyWinAssistant

Repository

The first open-source Artificial Narrow Intelligence generalist agentic framework Computer-Using-Agent that fully operates graphical-user-interfaces (GUIs) by using only natural language. Uses Visualization-of-Thought and Chain-of-Thought reasoning to elicit spatial reasoning and perception…

Browser & Computer Use Python Needs review MIT

Is PyWinAssistant safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.8 / 10
Provenance None
Signed commits 94%
Last push 630d ago
Compare PyWinAssistant

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

Pick any agent to compare →
Suggest a correction

In detail: PyWinAssistant scores 29.5/100 (Grade D), ranked #1339 of 1374 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 →

How PyWinAssistant 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.

Already done? Suggest a correctionAdd the trust badge
Active listing, but review is needed
  • [4.2.1] no meaningful activity in 12 months (last push 2025-02-13)

Chain of custody

Scanners check what the code says. This traces who ships PyWinAssistant and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/a-real-ai/pywinassistant, MIT, last pushed 2025-02-13. 94% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.8/10 (scanned Oct 29, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies2
    All 18 Scorecard checks
    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

  3. Published packages None

    No registry package. PyWinAssistant is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of PyWinAssistant.

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues PyWinAssistant’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.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How PyWinAssistant compares in Browser & Computer Use

  1. #41 OpenBrowser 32.0 +2.5
  2. #42 OpenCUA 31.6 +2.1
  3. #43 ScaleCUA 30.0 +0.5
  4. #44 PyWinAssistant 29.5 this agent
  5. #45 Open Operator 22.6 −6.9

Bars show each HVTrust score; the tick marks PyWinAssistant’s 29.5.

Where the 29.5 comes from

HVTrust dimensions vs the Browser & Computer Use average

29.5 / 100 · 100.0% confidence

PyWinAssistant Browser & Computer Use average (45 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
9.5 / 25
0.8 below avg 10.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.9 below avg 12.7
Transparency50% declared license · 50% OSSF Scorecard
11.7 / 17
in line with avg 12.0
Maintenance60% last-push freshness · 40% commit activity
0 / 20
12.2 below avg 12.2
AdoptionLog-scaled stars · package downloads
7.5 / 20
3.6 below avg 11.1

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-09
Rank Moved
Rank dropped 11 spots (#1310 → #1321)
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 630 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
View Browser & Computer Use Report missing data
29.4
Activity sub-score · out of 100
#44
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 →

Signals refreshed 2026-11-05 12:09 UTC · Repo last pushed 630 days ago — may be stale

Rank Trend

2026-09-29 2026-11-05

Activity & Reach

Stars
1.3k
Forks
191
Last Push
2025-02-13
630 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
10
Rank Change
=
was #1339

Analysis

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

Common questions about PyWinAssistant

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 630 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.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool 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-08-12
Tool Surface Changed
Detected tool/plugin surface changed: declared → none

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
Rank 19Surface 1
2026-10-09
Rank Moved
Rank dropped 11 spots (#1310 → #1321)
2026-09-23
Rank Moved
Rank dropped 522 spots (#771 → #1293)
2026-09-22
Rank Moved
Rank dropped 349 spots (#422 → #771)
2026-09-21
Rank Moved
Rank rose 870 spots (#1292 → #422)
2026-09-06
Rank Moved
Rank dropped 14 spots (#1250 → #1264)
2026-09-05
Rank Moved
Rank dropped 20 spots (#1230 → #1250)
2026-09-04
Rank Moved
Rank dropped 17 spots (#1213 → #1230)
2026-09-03
Rank Moved
Rank dropped 42 spots (#1171 → #1213)
2026-09-02
Rank Moved
Rank dropped 41 spots (#1130 → #1171)
2026-09-01
Rank Moved
Rank dropped 41 spots (#1089 → #1130)
2026-08-31
Rank Moved
Rank dropped 27 spots (#1062 → #1089)
2026-08-30
Rank Moved
Rank dropped 54 spots (#1008 → #1062)
2026-08-29
Rank Moved
Rank dropped 50 spots (#958 → #1008)
2026-08-28
Rank Moved
Rank dropped 35 spots (#923 → #958)
2026-08-27
Rank Moved
Rank dropped 26 spots (#897 → #923)
2026-08-26
Rank Moved
Rank dropped 108 spots (#789 → #897)
2026-08-16
Rank Moved
Rank dropped 16 spots (#770 → #786)
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-08-10
Rank Moved
Rank dropped 43 spots (#732 → #775)
2026-08-08
Rank Moved
Rank dropped 306 spots (#425 → #731)
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 29.5 Grade D
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.4 · Raw JSON