Is Pinme safe to use?

Pinme has an HVTrust score of 51.3/100 (Grade C), ranked #221 of 351 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Pinme?

Pinme scores 51.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 3.7k GitHub stars and is categorized under Agent Skills.

Pinme

glitternetwork/pinme

Deploy Your Frontend in a Single Command. Claude Code Skills supported.

Agent Skills TypeScript Listed MIT

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

OSSF Scorecard 4.2 / 10

Provenance None

Signed commits 13%

Last push 14d ago

Compare Pinme

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Pinme scores 51.3/100 (Grade C), ranked #221 of 351 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 4.2/10; 13% of recent commits are signed; last pushed 2026-09-12. Every point is earned from checkable signals — never paid placement. How scoring works →

How Pinme compares in Agent Skills

Bars show each HVTrust score; the tick marks Pinme’s 51.3.

Where the 51.3 comes from

HVTrust dimensions vs the Agent Skills average

51.3 / 100 · 100.0% confidence

Pinme Agent Skills average (351 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

5.9 / 25

2.2 below avg 8.1

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.6 below avg 11.4

Transparency50% declared license · 50% OSSF Scorecard

12.1 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

11.1 / 20

3.1 below avg 14.2

AdoptionLog-scaled stars · package downloads

11.7 / 20

2.7 above avg 9.0

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-25

Rank Moved

Rank dropped 21 spots (#202 → #223)

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Supabase

2026-09-23

Grade Changed

Trust grade D → C

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.2/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.

Compare with another agent Get email alerts for Pinme View Agent Skills Report missing data

55.9

Activity sub-score · out of 100

#221

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

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

3.7k

Forks

277

Last Push

2026-09-12

14 days ago

Commits (4 wk)

Downloads (7d)

206

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲2

was #223

Analysis

Activity Inputs

55.9 / 100

StarsRepository reach

21.4 / 30

FreshnessLast push recency

23.1 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

11.4 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.2 / 10

OpenSSF Scorecard · scanned Sep 23, 2026

Signed Commits

13%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 5

CII-Best-Practices 0

Code-Review 5

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 10

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 3

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Common questions about Pinme

Public trust evidence for Pinme 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 Pinme publish package provenance?

No published build provenance is currently detected for Pinme. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Pinme have an OpenSSF Scorecard?

Pinme has an OpenSSF Scorecard score of 4.2/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 Pinme actively maintained?

Maintained. Last push was 14 days ago.

What license does Pinme use?

Pinme ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Pinme's commits signed?

13% of the last 100 commits to Pinme 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

high confidence

1 detected

Public provider/service dependencies detected.

Supabase

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

medium confidence

1 tags

Broad capability areas detected.

filesystem

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

Provider Added

Runtime surface grew — new detected provider dependency: Supabase

Maintain Pinme?

For maintainers

HVTrust scores Pinme 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

2026-09-25

Rank Moved

Rank dropped 21 spots (#202 → #223)

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Supabase

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank rose 100 spots (#300 → #200)

2026-09-23

HVTrust Changed

HVTrust up 25.0pts (26.4 → 51.4)

2026-09-22

Newly Listed

First tracked at rank #300

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank rose 12 spots (#205 → #193)

2026-09-12

Grade Changed

Trust grade D → C

2026-09-12

Rank Moved

Rank rose 37 spots (#228 → #191)

2026-09-12

HVTrust Changed

HVTrust up 3.2pts (48.1 → 51.3)

2026-09-12

Activity Score Changed

Activity score up 7pts (51 → 58)

2026-09-11

Rank Moved

Rank dropped 11 spots (#217 → #228)

2026-09-05

Rank Moved

Rank dropped 12 spots (#172 → #184)

2026-09-02

Rank Moved

Rank dropped 16 spots (#143 → #159)

2026-08-31

Grade Changed

Trust grade C → D

2026-08-31

Rank Moved

Rank dropped 18 spots (#116 → #134)

2026-08-30

Rank Moved

Rank dropped 21 spots (#95 → #116)

2026-08-29

Rank Moved

Rank dropped 18 spots (#77 → #95)

2026-08-28

Rank Moved

Rank dropped 17 spots (#60 → #77)

2026-08-27

Rank Moved

Rank dropped 16 spots (#44 → #60)

2026-08-26

Scorecard Added

OSSF Scorecard: 4.2/10

2026-08-26

Grade Changed

Trust grade D → C

2026-08-26

HVTrust Changed

HVTrust up 22.7pts (27.6 → 50.3)

2026-08-11

Newly Listed

First tracked at rank #32

GitHub → npm: pinme

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/pinme.svg)](https://hvtracker.net/agents/pinme)
            
HTML:
            <a href="https://hvtracker.net/agents/pinme"><img src="https://hvtracker.net/badge/pinme.svg" alt="HVTrust"></a>

Other agents in Agent Skills

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