Opensquilla

OpenSquilla — Token-Efficient AI Agent with same budget, higher intelligence density

Agent Skills Python Listed Apache-2.0

Is Opensquilla safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.0 / 10
Provenance None
Signed commits 100%
Last push 2d ago
Advisories None known
Compare Opensquilla
Suggest a correction

In detail: Opensquilla scores 63.3/100 (Grade C), ranked #76 of 384 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.0/10; 100% of recent commits are signed; no published advisory affects its latest release (opensquilla); last pushed 2026-11-08. Every point is earned from checkable signals — never paid placement. How scoring works →

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

Chain of custody

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

  1. Source Signed

    github.com/TokenRhythm/opensquilla, Apache-2.0, last pushed 2026-11-08. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

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

    • Code Review2
    • Branch Protection4
    • Signed Releases0
    • Dangerous Workflow0
    • Token Permissions0
    • Pinned Dependencies1
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 4
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 2
    Contributors 3
    Dangerous-Workflow 0
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 1
    SAST 9
    Security-Policy 4
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 10
  3. Published packages Not linked

    • PyPI opensquilla Source link isn't a GitHub repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: opensquilla 0.3.0. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

  • 2026-08-27 OSSF Scorecard: 3.8/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

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

Verify this score yourself

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

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read the skill’s instructions for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you install it, such as Cisco Skill Scanner.

How Opensquilla compares in Agent Skills

  1. #74 Expo Skills 63.4 +0.1
  2. #75 Agent Plugins 63.3 ±0
  3. #76 Opensquilla 63.3 this agent
  4. #77 Archify 63.2 −0.1
  5. #78 Linkedin Skills 63.1 −0.2

Bars show each HVTrust score; the tick marks Opensquilla’s 63.3.

Where the 63.3 comes from

HVTrust dimensions vs the Agent Skills average

63.3 / 100 · 100.0% confidence

Opensquilla Agent Skills average (384 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
11.2 / 25
3.0 above avg 8.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.6 below avg 11.4
Transparency50% declared license · 50% OSSF Scorecard
12.8 / 17
0.6 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
5.9 above avg 14.0
AdoptionLog-scaled stars · package downloads
11.0 / 20
1.9 above avg 9.1

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-12
Rank Moved
Rank rose 10 spots (#83 → #73)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.0/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.
85.9
Activity sub-score · out of 100
#76

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

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed 2 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
7.1k
Forks
591
Last Push
2026-11-08
2 days ago
Commits (4 wk)
105
Downloads (7d)
20
pypi
HN mentions (30d)
—
Open Issues
191
Rank Change
▲8
was #84

Analysis

Activity Inputs

85.9 / 100
StarsRepository reach
23.1 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
12.9 / 20

Common questions about Opensquilla

Opensquilla has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Opensquilla publish package provenance?
No published build provenance is currently detected for Opensquilla. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Opensquilla have an OpenSSF Scorecard?
Opensquilla has an OpenSSF Scorecard score of 5.0/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 Opensquilla actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
What license does Opensquilla use?
Opensquilla ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Opensquilla's commits signed?
100% of the last 100 commits to Opensquilla 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
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
  • browser
  • shell
Detailed evidence is not shown in the public view.
Package Provenance Drift
low confidence
Unknown
Package source metadata is missing or inconclusive
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 Opensquilla'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-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: OpenAI, OpenRouter
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → declared
2026-09-20
Mcp Status Changed
Detected MCP server support changed: implemented → declared

Maintain Opensquilla?

For maintainers

HVTrust scores Opensquilla 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.

Reputation Timeline

Signal history
Rank 7Grade 4HVTrust 2MCP 2Scorecard 1Delisted 1Listed 1Surface 1Surface 1
2026-10-12
Rank Moved
Rank rose 10 spots (#83 → #73)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: OpenAI, OpenRouter
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → declared
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 153 spots (#224 → #71)
2026-09-23
HVTrust Changed
HVTrust up 29.6pts (33.4 → 63.0)
2026-09-22
Newly Listed
First tracked at rank #224
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Mcp Status Changed
Detected MCP server support changed: implemented → declared
2026-09-20
Grade Changed
Trust grade B → C
2026-09-20
Rank Moved
Rank dropped 10 spots (#59 → #69)
2026-09-18
Grade Changed
Trust grade C → B
2026-09-17
Rank Moved
Rank rose 10 spots (#68 → #58)
2026-09-05
Rank Moved
Rank dropped 15 spots (#40 → #55)
2026-08-27
Scorecard Added
OSSF Scorecard: 3.8/10
2026-08-27
Grade Changed
Trust grade D → C
2026-08-27
Rank Moved
Rank rose 48 spots (#76 → #28)
2026-08-27
HVTrust Changed
HVTrust up 26.2pts (36.6 → 62.8)
2026-08-26
Rank Moved
Rank dropped 51 spots (#25 → #76)

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 63.3 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/opensquilla.svg)](https://hvtracker.net/agents/opensquilla)
HTML:
<a href="https://hvtracker.net/agents/opensquilla"><img src="https://hvtracker.net/badge/opensquilla.svg" alt="HVTrust"></a>

Other agents in Agent Skills

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON