← Home

@types/color-convert

Stub TypeScript definitions entry for color-convert, which provides its own types definitions

7
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

types

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Dormancy followed by a stub/deprecation release is expected for @types packages when upstream adopts bundled types. Publisher has 10,437 approved packages and 0 rejections. ai
publish-pattern new-deps-added AI (publish-pattern): Adding color-convert as a dep is the correct stub pattern — ensures the real package (with bundled types) is installed when this stub is pulled in. ai
bogus-package bogus-package AI (bogus-package): All bogus-package signals are expected for a DefinitelyTyped deprecation stub: no code, no repo link, tiny payload. This is the standard pattern for @types stubs. ai
phantom-deps phantom-dep:color-convert AI (phantom-deps): Stub package intentionally declares color-convert as a dep without importing it — ensures the real package is installed. Not a phantom dep in the malicious sense. ai
source-diff source-size-dropped AI (source-diff): Source dropped to 0 because this version is a deprecation stub by design — prior versions had actual type definitions, this one intentionally has none. ai

Versions (showing 7 of 7)

Version Deps Published
3.0.1 1 / 0
2.0.4 1 / 0
2.0.3 1 / 0
2.0.2 1 / 0
2.0.1 1 / 0
2.0.0 1 / 0
1.9.0 1 / 0

v3.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.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. Consider requesting the maintainer enable provenance via CI/CD.