← Home

@pigment-css/vite-plugin

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:babel-plugin-define-var AI (phantom-deps): Used via Babel config convention, not direct import; stable pattern for this transform package. ai
phantom-deps phantom-dep:@babel/preset-typescript AI (phantom-deps): Framework-scoped Babel preset loaded by convention; expected for a TypeScript-aware transform plugin. ai

Versions (showing 19 of 19)

Version Deps Published
0.0.31 6 / 2
0.0.30 6 / 2
0.0.29 6 / 2
0.0.28 6 / 2
0.0.27 6 / 2
0.0.26 6 / 2
0.0.25 6 / 2
0.0.24 6 / 2
0.0.23 6 / 2
0.0.22 6 / 2
0.0.21 6 / 2
0.0.20 6 / 2
0.0.19 6 / 2
0.0.18 6 / 2
0.0.17 6 / 2
0.0.16 6 / 2
0.0.15 6 / 2
0.0.13 6 / 2
0.0.12 6 / 2

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

1 finding
LOW No provenance attestation provenance

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

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

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.