@dotcom-tool-kit/backend-serverless-app
A bootstrap plugin that provides the minimum required Tool Kit plugins for a "backend" (aka an [API](https://github.com/Financial-Times/next/wiki/Naming-Conventions#apis)) that is deployed to AWS. The plugins are:
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): Established FT org package; lack of Sigstore provenance is a process gap, not a security risk for this publisher. | ai | |
| phantom-deps | phantom-dep:@dotcom-tool-kit/npm | AI (phantom-deps): Sibling plugin in same monorepo; declared as dep for plugin resolution, not direct import. | ai | |
| phantom-deps | phantom-dep:@dotcom-tool-kit/node | AI (phantom-deps): Sibling plugin in same monorepo; declared as dep for plugin resolution, not direct import. | ai | |
| phantom-deps | phantom-dep:@dotcom-tool-kit/serverless | AI (phantom-deps): Sibling plugin in same monorepo; declared as dep for plugin resolution, not direct import. | ai | |
| phantom-deps | phantom-dep:@dotcom-tool-kit/circleci-deploy | AI (phantom-deps): Sibling plugin in same monorepo; declared as dep for plugin resolution, not direct import. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 6.0.10 | 4 / 0 | |
| 6.0.9 | 4 / 0 | |
| 6.0.8 | 4 / 0 | |
| 6.0.7 | 4 / 0 | |
| 6.0.6 | 4 / 0 | |
| 6.0.5 | 4 / 0 | |
| 6.0.4 | 4 / 0 | |
| 6.0.3 | 4 / 0 | |
| 6.0.2 | 4 / 0 | |
| 6.0.1 | 4 / 0 | |
| 6.0.0 | 4 / 0 |
v6.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.