@dotcom-tool-kit/containerised-app
A bootstrap plugin that provides the minimum required Tool Kit plugins for a containerised application that's deployed to Amazon Elastic Container Service (ECS).
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): FT's dotcom-tool-kit monorepo consistently publishes without Sigstore provenance; stable false positive for this package family. | ai | |
| phantom-deps | phantom-dep:@dotcom-tool-kit/node | AI (phantom-deps): Tool-kit plugin composition pattern; deps declared for orchestration, not direct import. | ai | |
| phantom-deps | phantom-dep:@dotcom-tool-kit/docker | AI (phantom-deps): Tool-kit plugin composition pattern; deps declared for orchestration, not direct import. | ai | |
| phantom-deps | phantom-dep:@dotcom-tool-kit/aws | AI (phantom-deps): Tool-kit plugin composition pattern; deps declared for orchestration, not direct import. | ai | |
| phantom-deps | phantom-dep:@dotcom-tool-kit/cloudsmith | AI (phantom-deps): Tool-kit plugin composition pattern; deps declared for orchestration, not direct import. | ai | |
| phantom-deps | phantom-dep:@dotcom-tool-kit/circleci-deploy | AI (phantom-deps): Tool-kit plugin composition pattern; deps declared for orchestration, not direct import. | ai | |
| phantom-deps | phantom-dep:@dotcom-tool-kit/doppler | AI (phantom-deps): Tool-kit plugin composition pattern; deps declared for orchestration, not direct import. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.0.11 | 9 / 0 | |
| 2.0.9 | 9 / 0 | |
| 2.0.8 | 9 / 0 | |
| 2.0.5 | 9 / 0 | |
| 2.0.4 | 9 / 0 | |
| 2.0.3 | 9 / 0 | |
| 2.0.0 | 9 / 0 |
v2.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.