Stakpak Agent

Ship your code, on autopilot. An open source agent that lives on your machines 24/7 and keeps your apps running. 🦀

Coding Agents Rust Grade D Listed Apache-2.0
44.9/100
Rank #355 of 468
Compare Stakpak Agent

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-07-06 · 31d ago
Recent change
Rank +1

Is Stakpak Agent safe? Stakpak Agent scores 44.9/100 (Grade D), ranked #355 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.5/10; 34% of recent commits are signed; last pushed 2026-07-06. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Coding Agents

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-05
Rank Moved
Rank dropped 19 spots (#336 → #355)
2026-08-05
Activity Score Changed
Activity score down 6pts (57 → 51)
2026-07-29
Rank Moved
Rank dropped 10 spots (#318 → #328)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.5/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.
Refresh maintenance signals The repo was last pushed 31 days ago. Fresh activity helps separate stable projects from stale ones.
50.7
Activity sub-score · out of 100
#43

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-08-06 05:00 UTC · Repo last pushed 31 days ago

Rank Trend

2026-07-05 2026-08-06

Activity & Reach

Stars
1.7k
Forks
179
Last Push
2026-07-06
31 days ago
Commits (4 wk)
0
Downloads (7d)
HN mentions (30d)
Open Issues
25
Rank Change
=
was #355

Analysis

HVTrust Dimensions vs Coding Agents

44.9 / 100 · 100.0% confidence

Stakpak Agent Coding Agents average (59 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.1 / 25
2.2 below avg 8.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.0 below avg 11.8
Transparency50% declared license · 50% OSSF Scorecard
11.5 / 17
in line with avg 11.3
Maintenance60% last-push freshness · 40% commit activity
9.9 / 20
4.8 below avg 14.7
AdoptionLog-scaled stars · package downloads
7.8 / 20
4.8 below avg 12.6

Activity Inputs

50.7 / 100
StarsRepository reach
19.4 / 30
FreshnessLast push recency
20.7 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
10.5 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
3.5 / 10
OpenSSF Scorecard · scanned Aug 5, 2026
Signed Commits
34%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 10
CII-Best-Practices 0
Code-Review 2
Contributors 3
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 0

Is Stakpak Agent safe?

Public trust evidence for Stakpak Agent 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 Stakpak Agent publish package provenance?
No published build provenance is currently detected for Stakpak Agent. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Stakpak Agent have an OpenSSF Scorecard?
Stakpak Agent has an OpenSSF Scorecard score of 3.5/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 Stakpak Agent actively maintained?
Slowing down. Last push was 31 days ago — keep an eye on whether activity resumes.
What license does Stakpak Agent use?
Stakpak Agent ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Stakpak Agent's commits signed?
34% of the last 100 commits to Stakpak Agent 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
high confidence
Implemented
Stakpak Agent appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
3 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.
  • code
  • search
  • shell
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 Stakpak Agent?

For maintainers

HVTrust scores Stakpak Agent 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 2Listed 1HVTrust 1Scorecard 1Score 1
2026-08-05
Rank Moved
Rank dropped 19 spots (#336 → #355)
2026-08-05
Activity Score Changed
Activity score down 6pts (57 → 51)
2026-07-29
Rank Moved
Rank dropped 10 spots (#318 → #328)
2026-07-15
Rank Moved
Rank dropped 23 spots (#283 → #306)
2026-07-14
Grade Changed
Trust grade C → D
2026-07-14
Rank Moved
Rank dropped 15 spots (#268 → #283)
2026-07-13
Rank Moved
Rank dropped 31 spots (#237 → #268)
2026-06-24
Rank Moved
Rank dropped 26 spots (#190 → #216)
2026-06-23
Scorecard Added
OSSF Scorecard: 3.6/10
2026-06-23
Grade Changed
Trust grade D → C
2026-06-23
Rank Moved
Rank rose 83 spots (#273 → #190)
2026-06-23
HVTrust Changed
HVTrust up 30.7pts (22.8 → 53.5)
2026-06-21
Newly Listed
First tracked at rank #270

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 44.9 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/stakpak-agent.svg)](https://hvtracker.net/agents/stakpak-agent)
HTML:
<a href="https://hvtracker.net/agents/stakpak-agent"><img src="https://hvtracker.net/badge/stakpak-agent.svg" alt="HVTrust"></a>

Other agents in Coding Agents

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