Is Skales safe to use?

Skales has an HVTrust score of 53.2/100 (Grade C), ranked #823 of 1328 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Skales?

Skales scores 53.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 1.9k GitHub stars and is categorized under Agent Frameworks.

Skales

skalesapp/skales

Personal AI desktop agent for Windows, macOS, Linux, Android & iOS. Set a goal, it works on its own. Teams (pair two des

Agent Frameworks TypeScript Grade C Listed NOASSERTION Source-available

53.2/100

Rank #823 of 1328

Compare Skales

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →

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

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-09-11 · 1d ago

Recent change

Rank +3

Is Skales safe? Skales scores 53.2/100 (Grade C), ranked #823 of 1328 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.1/10; recent commits are unsigned; last pushed 2026-09-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Frameworks

#74 IntentKit — 53.5 (C) → #75 Google AX — 53.3 (C) → #77 Agently — 52.8 (C) → #78 Verl Agent — 52.4 (C) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-09

Rank Moved

Rank dropped 22 spots (#805 → #827)

2026-09-08

Rank Moved

Rank dropped 16 spots (#789 → #805)

2026-09-07

Rank Moved

Rank dropped 38 spots (#751 → #789)

Maintainer Checklist

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

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for Skales View Agent Frameworks Report missing data

74.2

Activity sub-score · out of 100

#76

In Agent Frameworks

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C 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-08-11 2026-09-12

Activity & Reach

Stars

1.9k

Forks

259

Last Push

2026-09-11

yesterday

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲2

was #825

Analysis

HVTrust Dimensions vs Agent Frameworks

53.2 / 100 · 100.0% confidence

Skales Agent Frameworks average (122 agents)

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

3.9 / 25

5.8 below avg 9.7

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.8 below avg 11.6

Transparency50% declared license · 50% OSSF Scorecard

11.1 / 17

1.3 below avg 12.4

Maintenance60% last-push freshness · 40% commit activity

17.8 / 20

3.8 above avg 14.0

AdoptionLog-scaled stars · package downloads

7.9 / 20

3.3 below avg 11.2

Activity Inputs

74.2 / 100

StarsRepository reach

19.6 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

18.4 / 25

CommunityFork signal

11.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.1 / 10

OpenSSF Scorecard · scanned Sep 12, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 9

Maintained 10

Packaging -1

Pinned-Dependencies -1

SAST 0

Security-Policy 10

Signed-Releases 0

Token-Permissions -1

Vulnerabilities 0

Is Skales safe?

Source-available software. A lower HVTrust score reflects fewer public supply-chain artifacts (open license, build provenance, signed commits) — not a security finding. Skales may have internal security practices not visible through public signals.

Public trust evidence for Skales 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 Skales publish package provenance?

No published build provenance is currently detected for Skales. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Skales have an OpenSSF Scorecard?

Skales has an OpenSSF Scorecard score of 3.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 Skales actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Skales use?

Skales ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Skales's commits signed?

0% of the last 100 commits to Skales 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

medium confidence

Implemented

Skales appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

Google Gemini

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

Tool / Plugin Surface

high confidence

1 tags

Broad capability areas detected.

browser

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 Skales?

For maintainers

HVTrust scores Skales 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-09-09

Rank Moved

Rank dropped 22 spots (#805 → #827)

2026-09-08

Rank Moved

Rank dropped 16 spots (#789 → #805)

2026-09-07

Rank Moved

Rank dropped 38 spots (#751 → #789)

2026-09-05

Rank Moved

Rank dropped 69 spots (#681 → #750)

2026-09-04

Rank Moved

Rank dropped 36 spots (#645 → #681)

2026-09-03

Rank Moved

Rank dropped 83 spots (#562 → #645)

2026-09-02

Rank Moved

Rank dropped 17 spots (#545 → #562)

2026-09-01

Rank Moved

Rank dropped 11 spots (#534 → #545)

2026-08-31

Rank Moved

Rank dropped 35 spots (#499 → #534)

2026-08-29

Rank Moved

Rank dropped 22 spots (#481 → #503)

2026-08-27

Rank Moved

Rank dropped 12 spots (#463 → #475)

2026-08-26

Rank Moved

Rank dropped 50 spots (#413 → #463)

2026-08-24

Rank Moved

Rank dropped 18 spots (#396 → #414)

2026-08-22

Rank Moved

Rank rose 15 spots (#414 → #399)

2026-08-19

Rank Moved

Rank dropped 12 spots (#408 → #420)

2026-08-17

Rank Moved

Rank rose 12 spots (#419 → #407)

2026-08-13

Rank Moved

Rank dropped 13 spots (#399 → #412)

2026-08-12

Rank Moved

Rank rose 16 spots (#415 → #399)

2026-08-10

Rank Moved

Rank dropped 17 spots (#394 → #411)

2026-08-08

Rank Moved

Rank dropped 95 spots (#301 → #396)

2026-07-29

Scorecard Added

OSSF Scorecard: 3.1/10

2026-07-29

Grade Changed

Trust grade D → C

2026-07-29

Rank Moved

Rank rose 127 spots (#417 → #290)

2026-07-29

HVTrust Changed

HVTrust up 29.4pts (24.1 → 53.5)

2026-07-28

Newly Listed

First tracked at rank #417

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in Agent Frameworks

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