updated 2026-10-21 20:07 UTC

Skales

Repository Website

Personal AI agent for macOS, Windows, Linux, Android & iOS. Set a goal, it works alone: coding (Skales Code), desktop + browser automation, autonomous scheduled Tasks. Teams of agents and humans across paired desktops. Agent2Agent, MCP, computer use, voice, local LLMs (Ollama), Agent Skills…

Agent Frameworks Listed NOASSERTION Proprietary

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

OSSF Scorecard 4.1 / 10
Provenance None
Signed commits 0%
Last push 2d ago
Compare Skales

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Skales scores 54.3/100 (Grade C), ranked #867 of 1378 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 4.1/10; recent commits are unsigned; last pushed 2026-10-19. Every point is earned from checkable signals — never paid placement. How scoring works →

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

Chain of custody

Scanners check what the code says. This traces who ships Skales 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 Unsigned

    github.com/skalesapp/skales, NOASSERTION, last pushed 2026-10-19. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.

  2. Review and release Mixed

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

    • Code Review0
    • Branch Protection0
    • Signed Releases0
    • Dangerous Workflown/a
    • Token Permissionsn/a
    • Pinned Dependenciesn/a
    All 18 Scorecard checks
    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 10

  3. Published packages None

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

Changes to this chain

  • 2026-09-23 License classification changed from source-available to proprietary
  • 2026-07-29 OSSF Scorecard: 3.1/10

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 Skales’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 Skales compares in Agent Frameworks

  1. #81 Spring AI Alibaba 55.5 +1.2
  2. #82 agentos 54.4 +0.1
  3. #83 Skales 54.3 this agent
  4. #84 Agently 54.0 −0.3
  5. #85 Crabtalk 54.0 −0.3

Bars show each HVTrust score; the tick marks Skales’s 54.3.

Where the 54.3 comes from

HVTrust dimensions vs the Agent Frameworks average

54.3 / 100 · 100.0% confidence

Skales Agent Frameworks average (130 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.1 / 25
4.9 below avg 10.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.8 below avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
12.0 / 17
in line with avg 12.5
Maintenance60% last-push freshness · 40% commit activity
16.4 / 20
1.7 above avg 14.7
AdoptionLog-scaled stars · package downloads
8.0 / 20
3.2 below avg 11.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-18
Rank Moved
Rank dropped 13 spots (#851 → #864)
2026-10-17
Rank Moved
Rank dropped 23 spots (#828 → #851)
2026-10-15
Rank Moved
Rank dropped 11 spots (#824 → #835)
Maintainer Checklist
Declare an open license Publish a clear OSI-approved license so usage and maintenance terms are independently verifiable.
Raise Scorecard signals Current OSSF Scorecard is 4.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
70.6
Activity sub-score · out of 100
#83
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 →

Signals refreshed 2026-10-21 20:07 UTC · Repo last pushed 2 days ago

Rank Trend

2026-09-29 2026-10-21

Activity & Reach

Stars
2.2k
Forks
296
Last Push
2026-10-19
2 days ago
Commits (4 wk)
13
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
1
Rank Change
▼5
was #862

Analysis

Activity Inputs

70.6 / 100
StarsRepository reach
20.1 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
14.3 / 25
CommunityFork signal
11.5 / 20

Common questions about Skales

Proprietary 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 4.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 2 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
None detected
No clear third-party provider dependency 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 Skales'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-09-19
Provider Removed
Runtime surface shrank — no longer detected: Google Gemini

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
Rank 33Listed 1HVTrust 1Grade 1Scorecard 1Surface 1License 1
2026-10-18
Rank Moved
Rank dropped 13 spots (#851 → #864)
2026-10-17
Rank Moved
Rank dropped 23 spots (#828 → #851)
2026-10-15
Rank Moved
Rank dropped 11 spots (#824 → #835)
2026-10-12
Rank Moved
Rank rose 25 spots (#842 → #817)
2026-10-11
Rank Moved
Rank dropped 12 spots (#830 → #842)
2026-10-07
Rank Moved
Rank dropped 24 spots (#791 → #815)
2026-09-26
Rank Moved
Rank rose 74 spots (#838 → #764)
2026-09-23
License Changed
License classification changed from source-available to proprietary
2026-09-23
Rank Moved
Rank dropped 520 spots (#308 → #828)
2026-09-21
Rank Moved
Rank rose 532 spots (#832 → #300)
2026-09-19
Provider Removed
Runtime surface shrank — no longer detected: Google Gemini
2026-09-18
Rank Moved
Rank rose 22 spots (#858 → #836)
2026-09-15
Rank Moved
Rank dropped 11 spots (#841 → #852)
2026-09-12
Rank Moved
Rank dropped 11 spots (#825 → #836)
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 → Website →

Embed Badge Badge guide for maintainers →

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