← Home

@skbkontur/colors

npm
14
Versions
—
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

khlutkovatihonoveubitso4zhzzskbkontur-botfakefeikoriginal001templeoftemplarapocalyp0syslossirdpeshkinnibachmshatikhin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): @types/apca-w3 and @types/culori are type-only packages for color libraries; clearly in scope for a color token package. ai
source-diff large-new-source-files AI (source-diff): New files are color token CSS/JS/JSON outputs matching the package's declared exports; no suspicious code. ai
typosquat typosquat.levenshtein:cors AI (typosquat): Scoped package @skbkontur/colors is a color-token library; Levenshtein match to 'cors' is a false positive. ai
phantom-deps phantom-dep:@types/culori AI (phantom-deps): @types packages are type-only and not directly imported; stable false positive for this package. ai
phantom-deps phantom-dep:@types/apca-w3 AI (phantom-deps): @types packages are type-only and not directly imported; stable false positive for this package. ai

Versions (showing 14 of 14)

Version Deps Published
2.1.7 4 / 1
2.1.6 4 / 1
2.1.5 4 / 2
2.1.4 4 / 2
2.1.3 4 / 2
2.1.2 4 / 2
2.1.1 4 / 2
2.1.0 4 / 2
2.0.5 2 / 4
2.0.4 2 / 4
2.0.3 2 / 4
2.0.2 2 / 4
2.0.1 2 / 4
2.0.0 2 / 4

v2.1.6

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

1 finding
LOW No provenance attestation provenance

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

v2.1.4

1 finding
LOW No provenance attestation provenance

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

v2.1.3

1 finding
LOW No provenance attestation provenance

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

v2.1.2

1 finding
LOW No provenance attestation provenance

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

v2.1.1

1 finding
LOW No provenance attestation provenance

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

v2.1.0

1 finding
LOW No provenance attestation provenance

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

v2.0.5

1 finding
LOW No provenance attestation provenance

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

v2.0.4

1 finding
LOW No provenance attestation provenance

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

v2.0.3

1 finding
LOW No provenance attestation provenance

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

v2.0.2

1 finding
LOW No provenance attestation provenance

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

v2.0.1

1 finding
LOW No provenance attestation provenance

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

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.