updated 2026-10-05 00:09 UTC

Loopy

Repository Website

A library of practical AI-agent loops and an installable skill for finding, adapting, and designing repeatable agent workflows.

Agent Skills JavaScript Listed MIT

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

OSSF Scorecard 4.1 / 10
Provenance None
Signed commits 61%
Last push 24d ago
Compare Loopy

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Loopy scores 48.8/100 (Grade D), ranked #253 of 359 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; 61% of recent commits are signed; last pushed 2026-09-11. Every point is earned from checkable signals — never paid placement. How scoring works →

How Loopy 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 Loopy 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 and, for skills, AST02 Supply Chain Compromise.

  1. Source Partly signed

    github.com/Forward-Future/loopy, MIT, last pushed 2026-09-11. 61% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

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

    • Code Review0
    • Branch Protection3
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies3
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 3
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 6
    Packaging -1
    Pinned-Dependencies 3
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 10
    Vulnerabilities 0

  3. Published packages None

    No registry package. Loopy 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-10-01 OSSF Scorecard: 4.3/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 Loopy’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 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 Loopy compares in Agent Skills

  1. #251 Oh Dsh 48.9 +0.1
  2. #252 Skill Flow 48.9 +0.1
  3. #253 Loopy 48.8 this agent
  4. #254 Portaljs 48.8 ±0
  5. #255 Website Rebuild Skill 48.8 ±0

Bars show each HVTrust score; the tick marks Loopy’s 48.8.

Where the 48.8 comes from

HVTrust dimensions vs the Agent Skills average

48.8 / 100 · 100.0% confidence

Loopy Agent Skills average (359 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.2 / 25
in line with avg 8.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.6 below avg 11.4
Transparency50% declared license · 50% OSSF Scorecard
12.0 / 17
in line with avg 12.2
Maintenance60% last-push freshness · 40% commit activity
10.4 / 20
3.7 below avg 14.1
AdoptionLog-scaled stars · package downloads
8.4 / 20
0.6 below avg 9.0

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-01
Scorecard Added
OSSF Scorecard: 4.3/10
2026-10-01
Rank Moved
Rank rose 110 spots (#357 → #247)
2026-10-01
HVTrust Changed
HVTrust up 29.8pts (19.7 → 49.5)
Maintainer Checklist
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.
Compare with another agent Get email alerts for Loopy View Agent Skills Report missing data
54.2
Activity sub-score · out of 100
#253
In Agent Skills

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-10-05 00:09 UTC · Repo last pushed 24 days ago

Rank Trend

2026-09-29 2026-10-04

Activity & Reach

Stars
3.2k
Forks
281
Last Push
2026-09-11
24 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
2
Rank Change
=
was #253

Analysis

Activity Inputs

54.2 / 100
StarsRepository reach
21.0 / 30
FreshnessLast push recency
21.7 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
11.4 / 20

Common questions about Loopy

Public trust evidence for Loopy 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 Loopy publish package provenance?
No published build provenance is currently detected for Loopy. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Loopy have an OpenSSF Scorecard?
Loopy 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 Loopy actively maintained?
Maintained. Last push was 24 days ago.
What license does Loopy use?
Loopy ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Loopy's commits signed?
61% of the last 100 commits to Loopy 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
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
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

Maintain Loopy?

For maintainers

HVTrust scores Loopy 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
Listed 1HVTrust 1Rank 1Scorecard 1
2026-10-01
Scorecard Added
OSSF Scorecard: 4.3/10
2026-10-01
Rank Moved
Rank rose 110 spots (#357 → #247)
2026-10-01
HVTrust Changed
HVTrust up 29.8pts (19.7 → 49.5)
2026-09-29
Newly Listed
First tracked at rank #357
GitHub → Website →

Embed Badge Badge guide for maintainers →

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

Other agents in Agent Skills

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