gsd-build/get-shit-done

COLLECTIONattested
v1.42.3gsd-buildMITUpdated 4mo agonpmGitHub

A light-weight and powerful meta-prompting, context engineering and spec-driven development system for Claude Code by TÂCHES.

This repository is no longer the active home for GSD development. The project now continues as GSD Core in the Open GSD repository: Use the new repository for current source code, issues, releases, and contribution

This collection bundles
37 agents

⚠ The trust score below reflects the installer package get-shit-done-cc only. The bundled units are not individually verified or scanned — review them before use.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
10kDownloads/wk
64kGitHub stars
5kForks
4mo agoLast update
Package
Authorgsd-build
LicenseMIT
Version1.42.3
Sourcegithub
npmget-shit-done-cc
GitHubgsd-build/get-shit-done
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 7dfeb7a
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface—
Security scan✓ Cleanv1.42.3 · 1mo agoHow well does this scan work?
EvalsNone
IndexedJun 14, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source1mo ago

Forge read 300 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

This repository is no longer the active home for GSD development. The project now continues as GSD Core in the Open GSD repository: Use the new repository for current source code, issues, releases, and contribution

Keywords
claude-codecontext-engineeringmeta-promptingspec-driven-developmentcollection
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-08-28 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

58 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+46 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies, optionalDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.