← Home

@dotcom-tool-kit/component

npm Repository Homepage

A bootstrap plugin that provides the minimum required Tool Kit plugins for a "component" (aka an [npm module](https://github.com/Financial-Times/next/wiki/Naming-Conventions#npm-modules)). The plugins are:

6
Versions
ISC
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

quartertothe-ftrobertboulton

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Established FT org package; lack of provenance is common and not a risk signal here. ai
phantom-deps phantom-dep:@dotcom-tool-kit/npm AI (phantom-deps): Plugin package that declares deps for consumers to use; not directly imported by design. ai
phantom-deps phantom-dep:@dotcom-tool-kit/circleci-npm AI (phantom-deps): Same pattern — plugin re-exports sibling deps; stable false positive for this package. ai

Versions (showing 6 of 6)

Version Deps Published
7.0.5 2 / 0
7.0.4 2 / 0
7.0.3 2 / 0
7.0.2 2 / 0
7.0.1 2 / 0
7.0.0 2 / 0

v7.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v7.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v7.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v7.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.