← Home

@pigment-css/react

npm Repository Homepage
19
Versions
—
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

oliviertassinarisiriwatknpdiegoandaimj12albertaarongarciahmnajdovabrijeshb42

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@emotion/react AI (phantom-deps): CSS-in-JS library; @emotion/react is a legitimate runtime dep used via config/peer patterns, not direct imports. ai
phantom-deps phantom-dep:@emotion/styled AI (phantom-deps): CSS-in-JS library; @emotion/styled is a legitimate runtime dep used via config/peer patterns, not direct imports. ai

Versions (showing 19 of 19)

Version Deps Published
0.0.31 22 / 16
0.0.30 22 / 16
0.0.29 22 / 16
0.0.28 22 / 16
0.0.27 21 / 17
0.0.26 21 / 17
0.0.25 21 / 17
0.0.24 21 / 17
0.0.23 21 / 17
0.0.22 21 / 17
0.0.21 21 / 17
0.0.20 21 / 17
0.0.19 21 / 17
0.0.18 21 / 17
0.0.17 21 / 17
0.0.16 21 / 17
0.0.15 21 / 17
0.0.13 21 / 16
0.0.12 21 / 16

v0.0.29

1 finding
LOW No provenance attestation provenance

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

v0.0.28

1 finding
LOW No provenance attestation provenance

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

v0.0.27

1 finding
LOW No provenance attestation provenance

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

v0.0.26

1 finding
LOW No provenance attestation provenance

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

v0.0.25

1 finding
LOW No provenance attestation provenance

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

v0.0.24

1 finding
LOW No provenance attestation provenance

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

v0.0.23

1 finding
LOW No provenance attestation provenance

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

v0.0.22

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: siriwatknp → brijeshb42 (on 2024-09-04, known maintainer) provenance

This version was published by a different npm account (brijeshb42) than the most recent previously approved version (siriwatknp) on 2024-09-04, but brijeshb42 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.0.21

1 finding
LOW No provenance attestation provenance

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

v0.0.20

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: brijeshb42 → siriwatknp (on 2024-08-08, known maintainer) provenance

This version was published by a different npm account (siriwatknp) than the most recent previously approved version (brijeshb42) on 2024-08-08, but siriwatknp is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.0.19

1 finding
LOW No provenance attestation provenance

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

v0.0.18

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: siriwatknp → brijeshb42 (on 2024-07-25, known maintainer) provenance

This version was published by a different npm account (brijeshb42) than the most recent previously approved version (siriwatknp) on 2024-07-25, but brijeshb42 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.0.17

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: siriwatknp → brijeshb42 (on 2024-07-10, known maintainer) provenance

This version was published by a different npm account (brijeshb42) than the most recent previously approved version (siriwatknp) on 2024-07-10, but brijeshb42 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.0.16

1 finding
LOW No provenance attestation provenance

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

v0.0.15

1 finding
LOW No provenance attestation provenance

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

v0.0.13

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.

v0.0.12

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.