@bigcommerce/create-catalyst
Create a new Catalyst project, and optionally connect the project to a BigCommerce store. Add `--help` to the end of any command to learn about available subcommands and options.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:giget | AI (phantom-deps): giget is declared and used as a direct dependency; phantom-dep heuristic is a false positive. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): commander is declared and used indirectly via @commander-js/extra-typings; stable false positive. | ai | |
| phantom-deps | phantom-dep:@inquirer/type | AI (phantom-deps): @inquirer/type is declared and used indirectly via @inquirer/prompts; stable false positive. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.0.3 | 23 / 17 | |
| 1.0.2 | 23 / 17 | |
| 1.0.1 | 23 / 17 | |
| 1.0.0 | 23 / 17 |
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.