@dotcom-tool-kit/circleci
This plugin manages Tool Kit commands that are run from CircleCI workflows, via a Tool Kit [`Hook`](#hooks) that automatically manages `.circleci/config.yml`. It also exposes state from the CircleCI environment for other plugins to consume generically.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@dotcom-tool-kit/base | AI (dependencies): Same FT monorepo sibling; trusted publisher with 85 approved packages. | ai | |
| dependencies | unvetted-dep:@dotcom-tool-kit/error | AI (dependencies): Same FT monorepo sibling; trusted publisher with 85 approved packages. | ai | |
| dependencies | unvetted-dep:@dotcom-tool-kit/logger | AI (dependencies): Same FT monorepo sibling; trusted publisher with 85 approved packages. | ai | |
| provenance | no-provenance | AI (provenance): Established FT monorepo package; lack of provenance is consistent across all versions and not a risk indicator here. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 9.2.1 | 10 / 7 | |
| 9.2.0 | 10 / 7 | |
| 9.1.1 | 10 / 7 | |
| 9.1.0 | 10 / 7 | |
| 9.0.1 | 10 / 7 | |
| 9.0.0 | 10 / 7 | |
| 8.1.0 | 10 / 6 |
v9.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.