← Home

@dotcom-tool-kit/circleci-npm

This plugin is for managing the `publish:tag` hook that is run from circleci to publish the built package to the npm registry.

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
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a declared runtime dep in a TypeScript monorepo plugin; indirect import is expected. ai
phantom-deps phantom-dep:@dotcom-tool-kit/npm AI (phantom-deps): Same-org monorepo sibling; re-exported/composed rather than directly imported is normal for this plugin pattern. ai
phantom-deps phantom-dep:@dotcom-tool-kit/circleci AI (phantom-deps): Same-org monorepo sibling; same reasoning as @dotcom-tool-kit/npm above. ai

Versions (showing 6 of 6)

Version Deps Published
8.0.5 3 / 1
8.0.4 3 / 1
8.0.3 3 / 1
8.0.2 3 / 1
8.0.1 3 / 1
8.0.0 3 / 1

v8.0.5

1 finding
LOW No provenance attestation provenance

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

v8.0.4

1 finding
LOW No provenance attestation provenance

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

v8.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.

v8.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.

v8.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.

v8.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.