Building CLI plugins, IDE extensions, or dev SDKs? GreatCTO auto-detects the devtools archetype and ships OpenSSF Scorecard, SOC2 Type 2, signed releases, and telemetry-leak prevention gates from day one.
package.json + .github/workflows/release.yml →Compliance auto-suggested: openssf · soc2-type-2 · gdpr. Specialist agents activated:
Sigstore signing · SLSA Level 3 · provenance · Dependabot · OpenSSF Scorecard ≥ 7 · npm provenance · pinned actions in CI.
No paths · no usernames · no source · opt-in default · revocable consent · GDPR-compliant identifiers (UUID, no IP).
Backward compat to last 3 majors · Node 18/20/22 · Python 3.10/3.11/3.12 · IDE: VS Code current+1, JetBrains current+1.
Locked dependencies · pinned actions · deterministic build outputs · binary diff verification on releases.
Packs auto-attach when CLI detects pack-specific signals (e.g. twilio in deps → voice-pack). Each pack adds its own reviewer agents + human gates on top of the base archetype pipeline.
20 startups in this space. Click for full pack mapping.
Listed companies operate in this space. Inclusion is based on publicly available product descriptions and does not imply endorsement of or by GreatCTO.
$ npx great-cto init