Is Vibe Coding Prompt Template safe to use?

Vibe Coding Prompt Template has an HVTrust score of 54.4/100 (Grade C), ranked #168 of 351 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Vibe Coding Prompt Template?

Vibe Coding Prompt Template scores 54.4/100 on HVTracker's evidence-weighted HVTrust scale. It has 3.1k GitHub stars and is categorized under Agent Skills.

Vibe Coding Prompt Template

KhazP/vibe-coding-prompt-template

Templates and workflow for generating PRDs, Tech Designs, and MVP and more using LLMs for AI IDEs

Agent Skills TypeScript Listed MIT

Is Vibe Coding Prompt Template safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 5.2 / 10

Provenance None

Signed commits 36%

Last push 16d ago

Compare Vibe Coding Prompt Template

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Vibe Coding Prompt Template scores 54.4/100 (Grade C), ranked #168 of 351 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 5.2/10; 36% of recent commits are signed; last pushed 2026-09-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How Vibe Coding Prompt Template compares in Agent Skills

#166 Cc Sdd 54.6 +0.2
#167 Agent Skill Creator 54.5 +0.1
#168 Vibe Coding Prompt Template 54.4 this agent
#169 Aws Agent Skills 54.4 ±0
#170 OpenBiliClaw 54.4 ±0

Bars show each HVTrust score; the tick marks Vibe Coding Prompt Template’s 54.4.

Where the 54.4 comes from

HVTrust dimensions vs the Agent Skills average

54.4 / 100 · 100.0% confidence

Vibe Coding Prompt Template Agent Skills average (351 agents)

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

8.3 / 25

in line with 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.9 / 17

0.7 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

14.0 / 20

in line with avg 14.2

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

Rank Moved

Rank dropped 17 spots (#153 → #170)

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank dropped 64 spots (#90 → #154)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.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 Vibe Coding Prompt Template View Agent Skills Report missing data

65.6

Activity sub-score · out of 100

#168

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

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

3.1k

Forks

385

Last Push

2026-09-10

16 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲2

was #170

Analysis

Activity Inputs

65.6 / 100

StarsRepository reach

21.0 / 30

FreshnessLast push recency

22.8 / 25

ActivityRecent commits

9.7 / 25

CommunityFork signal

12.0 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.2 / 10

OpenSSF Scorecard · scanned Sep 24, 2026

Signed Commits

36%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 5

SAST 0

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 10

Common questions about Vibe Coding Prompt Template

Public trust evidence for Vibe Coding Prompt Template 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 Vibe Coding Prompt Template publish package provenance?

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

Does Vibe Coding Prompt Template have an OpenSSF Scorecard?

Vibe Coding Prompt Template has an OpenSSF Scorecard score of 5.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 Vibe Coding Prompt Template actively maintained?

Maintained. Last push was 16 days ago.

What license does Vibe Coding Prompt Template use?

Vibe Coding Prompt Template ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Vibe Coding Prompt Template's commits signed?

36% of the last 100 commits to Vibe Coding Prompt Template 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

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 Vibe Coding Prompt Template?

For maintainers

HVTrust scores Vibe Coding Prompt Template 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 17 spots (#153 → #170)

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank dropped 64 spots (#90 → #154)

2026-09-23

HVTrust Changed

HVTrust up 10.2pts (44.4 → 54.6)

2026-09-22

Newly Listed

First tracked at rank #90

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-19

Rank Moved

Rank dropped 28 spots (#121 → #149)

2026-09-19

Activity Score Changed

Activity score down 7pts (75 → 68)

2026-09-02

Rank Moved

Rank dropped 10 spots (#68 → #78)

2026-08-30

Scorecard Added

OSSF Scorecard: 5.1/10

2026-08-30

Grade Changed

Trust grade D → C

2026-08-30

Rank Moved

Rank rose 159 spots (#216 → #57)

2026-08-30

HVTrust Changed

HVTrust up 34.2pts (23.8 → 58.0)

2026-08-29

Rank Moved

Rank dropped 29 spots (#187 → #216)

2026-08-28

Rank Moved

Rank dropped 23 spots (#164 → #187)

2026-08-27

Rank Moved

Rank dropped 18 spots (#146 → #164)

2026-08-26

Rank Moved

Rank dropped 78 spots (#68 → #146)

2026-08-20

Rank Moved

Rank rose 55 spots (#122 → #67)

2026-08-20

HVTrust Changed

HVTrust up 3.9pts (20.1 → 24.0)

2026-08-20

Activity Score Changed

Activity score up 22pts (53 → 75)

2026-08-17

Rank Moved

Rank dropped 11 spots (#111 → #122)

2026-08-17

Activity Score Changed

Activity score down 8pts (61 → 53)

2026-08-16

Rank Moved

Rank dropped 10 spots (#101 → #111)

2026-08-11

Newly Listed

First tracked at rank #98

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/vibe-coding-prompt-template.svg)](https://hvtracker.net/agents/vibe-coding-prompt-template)
            
HTML:
            <a href="https://hvtracker.net/agents/vibe-coding-prompt-template"><img src="https://hvtracker.net/badge/vibe-coding-prompt-template.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.3 · Raw JSON