@usethrottle/cli
Throttle command-line tool — connect your BigCommerce store, manage embed config, manage your account
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Minor publish-env drift, no attestation regression observed. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Sentry SDK is a well-known, benign dependency. | ai | |
| provenance | no-provenance | AI (provenance): CLI tool with no install scripts or suspicious code; provenance absence is a process gap, not a security risk for this package. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @usethrottle/cli is unrelated to joi; levenshtein match is coincidental. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.0.1 | 4 / 7 | |
| 2.0.0 | 5 / 6 | |
| 1.0.4 | 4 / 6 | |
| 1.0.3 | 4 / 6 | |
| 1.0.2 | 4 / 6 | |
| 1.0.1 | 3 / 5 | |
| 1.0.0 | 3 / 5 | |
| 0.2.0 | 3 / 5 | |
| 0.1.0 | 3 / 5 |
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: thejoud.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.