← Home

@rescui/colors

npm
18
Versions
Apache-2.0
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

jetbrains-adminjetbrains-buildserveralmsh

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): JetBrains org migrating from jetbrains-buildserver to GitHub Actions CI publisher; consistent with documented CI/CD transitions across JetBrains packages. ai
typosquat typosquat.levenshtein:cors AI (typosquat): @rescui/colors is a JetBrains color utility; name similarity to 'cors' is coincidental and not a typosquat. ai
bogus-package bogus-package AI (bogus-package): Scoped JetBrains corporate package; sparse metadata is typical for internal CI-published libraries. ai

Versions (showing 18 of 18)

Version Deps Published
0.3.2 0 / 10
0.3.1 0 / 10
0.3.0 0 / 10
0.2.12 0 / 10
0.2.11 0 / 10
0.2.10 0 / 10
0.2.9 0 / 10
0.2.8 0 / 10
0.2.7 0 / 10
0.2.6 0 / 10
0.2.5 0 / 10
0.2.4 0 / 10
0.2.3 0 / 10
0.2.2 0 / 10
0.2.1 0 / 10
0.2.0 0 / 10
0.1.11 0 / 9
0.1.10 0 / 9

v0.3.2

1 finding
LOW No provenance attestation provenance

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

v0.3.1

1 finding
LOW No provenance attestation provenance

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

v0.2.7

1 finding
LOW No provenance attestation provenance

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

v0.2.6

1 finding
LOW No provenance attestation provenance

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

v0.2.5

1 finding
LOW No provenance attestation provenance

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

v0.2.4

1 finding
LOW No provenance attestation provenance

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

v0.2.3

1 finding
LOW No provenance attestation provenance

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

v0.2.2

1 finding
LOW No provenance attestation provenance

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

v0.2.1

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.1.11

1 finding
LOW No provenance attestation provenance

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

v0.1.10

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.