RepoTrust

soumatheusgomes/vibe-coding-toolkit

A curated, battle-tested AI-coding toolkit: Claude Code plugins, subagent orchestration, quality gates, and ready-to-copy prompts, extracted from real production use.

https://github.com/soumatheusgomes/vibe-coding-toolkit · commit 7ef68dd7b00d · scored 2026-11-14 · scoring prov-4+qual-2+sec-2

RepoTrust ai badge RepoTrust quality badge RepoTrust security badge

Dispute this score or request a re-score Full report JSON

Scores

Pillar Score Signal Confidence Coverage
AI provenance (estimated AI-generated share) 42 explicit 79% 100%
Code quality 75 adequate 90% 100%
Security 84 adequate 85% 100%

AI provenance

Explicit AI attribution on 42% of first-party code added; an estimated 42% including velocity signals.

AI tool Attributed commits Lines added
Claude Code 14 554

Current source lines last changed by AI-attributed commits: 539 of 1,098.

Findings per 1,000 lines AI-attributed Other Ratio
Quality 0.0 7.156 0.0x
Security 0.0 1.789 0.0x
Month Lines added Attributed to AI
2026-09 554 100%
2026-10 757 0%

Evidence

AI provenance describes how code was produced; it is not a quality judgment. Unless attribution is explicit, these are signals consistent with AI generation, not proof. Squash/rebase workflows, imported code, and rewritten history reduce accuracy.

Code quality

Code quality is adequate: test-to-source ratio 0.11, no CI test run detected; 0% of function code in complex or long functions; 1% duplicated lines. Weakest area: testing.

Area Score
Complexity (lizard) 100
Duplication 92
Code smells (Opengrep) 80
Tests and CI 48
Documentation 65
Type safety n/a
Process (Scorecard review/maintenance) n/a

Security

Security posture is adequate: no high-impact findings. Weakest area: posture.

Area Score
Secrets (gitleaks, tree + history) 100
Static analysis (Opengrep) 92
Vulnerable dependencies (OSV) n/a
CI workflows (zizmor) 100
Posture (policy, updates, signing, lockfiles) 0
OpenSSF Scorecard n/a

Top findings

Severity Finding Location
medium opengrep/javascript.lang.security.insecure-object-assign: Depending on the context, user control data in Object.assign can cause web response to include data that it should not have or can lead to a mass assignment vulnerability. [confidence low] scripts/validate-next.mjs:245

Static signals only: the scorer never runs the project's code. Secret findings are pattern matches that were not verified, and secret values are never stored.

Repository profile

Language Lines
JavaScript 1,219

Embed a badge

Maintainers can show these in a README. Badges update when the repository is re-scored.

[![RepoTrust ai](https://repotrust.synapticcyber.com/badge/github.com/soumatheusgomes/vibe-coding-toolkit/ai.svg)](https://repotrust.synapticcyber.com/r/github.com/soumatheusgomes/vibe-coding-toolkit/)
[![RepoTrust quality](https://repotrust.synapticcyber.com/badge/github.com/soumatheusgomes/vibe-coding-toolkit/quality.svg)](https://repotrust.synapticcyber.com/r/github.com/soumatheusgomes/vibe-coding-toolkit/)
[![RepoTrust security](https://repotrust.synapticcyber.com/badge/github.com/soumatheusgomes/vibe-coding-toolkit/security.svg)](https://repotrust.synapticcyber.com/r/github.com/soumatheusgomes/vibe-coding-toolkit/)