PocketFlow

Pocket Flow: 100-line LLM framework. Let Agents build Agents!

Agent Frameworks Python Grade D Listed MIT
46.3/100
Rank #340 of 468
Compare PocketFlow

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-26 · 11d ago
Recent change
No recent signal change

Is PocketFlow safe? PocketFlow scores 46.3/100 (Grade D), ranked #340 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 2.3/10; 37% of recent commits are signed; last pushed 2026-07-26. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Frameworks

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-07-29
Rank Moved
Rank dropped 10 spots (#326 → #336)
2026-07-26
Activity Resumed
Activity resumed
2026-07-26
Rank Moved
Rank rose 52 spots (#372 → #320)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.3/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.
66.0
Activity sub-score · out of 100
#71

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 11 days ago

Rank Trend

2026-07-05 2026-08-06

Activity & Reach

Stars
11.1k
Forks
1.2k
Last Push
2026-07-26
11 days ago
Commits (4 wk)
1
Downloads (7d)
HN mentions (30d)
Open Issues
61
Rank Change
=
was #340

Analysis

HVTrust Dimensions vs Agent Frameworks

46.3 / 100 · 100.0% confidence

PocketFlow Agent Frameworks average (103 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.7 / 25
4.3 below avg 9.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
10.5 / 17
1.5 below avg 12.0
Maintenance60% last-push freshness · 40% commit activity
12.5 / 20
2.1 below avg 14.6
AdoptionLog-scaled stars · package downloads
9.7 / 20
2.2 below avg 11.9

Activity Inputs

66.0 / 100
StarsRepository reach
24.3 / 30
FreshnessLast push recency
23.5 / 25
ActivityRecent commits
3.8 / 25
CommunityFork signal
14.3 / 20

Supply Chain Trust

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

Is PocketFlow safe?

Public trust evidence for PocketFlow 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 PocketFlow publish package provenance?
No published build provenance is currently detected for PocketFlow. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does PocketFlow have an OpenSSF Scorecard?
PocketFlow has an OpenSSF Scorecard score of 2.3/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 PocketFlow actively maintained?
Maintained. Last push was 11 days ago.
What license does PocketFlow use?
PocketFlow ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are PocketFlow's commits signed?
37% of the last 100 commits to PocketFlow 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
3 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
3 tags
Broad capability areas 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
How this surface has changed

Detected changes to PocketFlow'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-07-26
Activity Resumed
Activity resumed
2026-06-25
Activity Went Stale
No commits for 90 days

Maintain PocketFlow?

For maintainers

HVTrust scores PocketFlow 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 7HVTrust 2Listed 1Scorecard 1Stale 1Score 1Fresh 1
2026-07-29
Rank Moved
Rank dropped 10 spots (#326 → #336)
2026-07-26
Activity Resumed
Activity resumed
2026-07-26
Rank Moved
Rank rose 52 spots (#372 → #320)
2026-07-26
HVTrust Changed
HVTrust up 9.2pts (37.8 → 47.0)
2026-07-26
Activity Score Changed
Activity score up 21pts (47 → 67)
2026-07-15
Rank Moved
Rank dropped 24 spots (#344 → #368)
2026-07-14
Rank Moved
Rank dropped 19 spots (#325 → #344)
2026-07-13
Rank Moved
Rank dropped 36 spots (#289 → #325)
2026-06-25
Activity Went Stale
No commits for 90 days
2026-06-24
Rank Moved
Rank dropped 31 spots (#242 → #273)
2026-06-23
Scorecard Added
OSSF Scorecard: 2.3/10
2026-06-23
Rank Moved
Rank rose 50 spots (#292 → #242)
2026-06-23
HVTrust Changed
HVTrust up 23.3pts (18.5 → 41.8)
2026-06-21
Newly Listed
First tracked at rank #291

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 46.3 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/pocketflow.svg)](https://hvtracker.net/agents/pocketflow)
HTML:
<a href="https://hvtracker.net/agents/pocketflow"><img src="https://hvtracker.net/badge/pocketflow.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.2 · Raw JSON