@dotcom-tool-kit/conflict No license 2 versions

@dotcom-tool-kit/conflict

npm

Versions

—

License

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.

Source	Rule	Reason	Accepted by	When
bogus-package	bogus-package	AI (bogus-package): Internal utility in the @dotcom-tool-kit scoped family; sparse metadata is a consistent pattern across all packages in this suite.	ai	2026/05/21
npm-metadata	no-description	AI (npm-metadata): Consistent with other @dotcom-tool-kit packages; not indicative of malice.	ai	2026/05/21

Versions (showing 2 of 2)

Version	Deps	Published
2.0.1	1 / 0	2026-01-15
2.0.0	1 / 0	2025-10-31

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

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