Building an npm, PyPI, crates.io, or Maven library? GreatCTO auto-detects the library archetype and ships semver enforcement, API stability checks, changelog discipline, and migration guides from day one.
package.json with "main" + "exports" →No regulatory compliance — but TDD, 12-angle review, security audit, and supply-chain hardening still apply:
Detects breaking changes via api-extractor / pyright / cargo public-api. Forces semver alignment.
Tests against last 3 major versions of consumers. Snapshot diff on type definitions. Bundle-size regression checked.
Conventional commits → auto-generate CHANGELOG.md · Keep a Changelog format · migration guides for major bumps.
npm audit · cargo audit · Dependabot · OpenSSF Scorecard · provenance checks at publish time.
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.
2 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