updated 2026-10-09 08:15 UTC

PipesHub

Repository
Memory & Knowledge Listed

Evidence is still being collected. PipesHub hasn't had its first full check yet: 0 of the 5 signals its score is built from are in (still to fetch: GitHub activity, OSSF Scorecard, package downloads, provenance and signed commits), so the score is provisional and no grade is shown.

GitHub activity pending
OSSF Scorecard pending
Package downloads pending
Provenance pending
Signed commits pending
Compare PipesHub

How does it stack up against its Memory & Knowledge neighbours?

Pick any agent to compare →
Suggest a correction

How PipesHub compares in Memory & Knowledge

  1. #45 LycheeMemory 41.5 +41.5
  2. #46 Utopia 28.8 +28.8
  3. #47 Memmy 0.0 ±0
  4. #49 Tigerless Agent Memory 0.0 ±0

Bars show each HVTrust score; the tick marks PipesHub’s 0.0.

Where the 0.0 comes from

HVTrust dimensions vs the Memory & Knowledge average

0.0 / 100 · provisional

PipesHub Memory & Knowledge average (49 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
0 / 25
11.2 below avg 11.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.8 below avg 12.6
Transparency50% declared license · 50% OSSF Scorecard
0 / 17
12.1 below avg 12.1
Maintenance60% last-push freshness · 40% commit activity
0 / 20
16.1 below avg 16.1
AdoptionLog-scaled stars · package downloads
0 / 20
12.7 below avg 12.7

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-10-09
Newly Listed
First tracked at rank #1356
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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 999 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for PipesHub View Memory & Knowledge Report missing data
0.0
Activity sub-score · out of 100
#48
In Memory & Knowledge

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

Signals refreshed 2026-10-09 08:15 UTC · Repo last pushed 999 days ago — may be stale

Activity & Reach

Stars
0
Forks
0
Last Push
pending
999 days ago
Commits (4 wk)
—
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
0
Rank Change
—

Analysis

Activity Inputs

0.0 / 100
StarsRepository reach
0.0 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
0.0 / 20

Common questions about PipesHub

Public trust evidence for PipesHub 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 PipesHub publish package provenance?
No published build provenance is currently detected for PipesHub. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does PipesHub have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for PipesHub. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is PipesHub actively maintained?
Stale. The repository has not been pushed to in 999 days. Consider whether the project is still being maintained.
What license does PipesHub use?
PipesHub ships under no SPDX license detected. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

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

Maintain PipesHub?

For maintainers

HVTrust scores PipesHub 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 1
2026-10-09
Newly Listed
First tracked at rank #1356
GitHub →

Embed Badge Badge guide for maintainers →

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

Other agents in Memory & Knowledge

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