@csszyx/unplugin
Vite and Webpack integration for csszyx
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): postcss-value-parser and proper-lockfile are legitimate, established packages fitting the CSS plugin use case. | ai | |
| dependencies | unvetted-dep:@csszyx/vue-adapter | AI (dependencies): Workspace sibling from the same csszyx monorepo; not an external untrusted dependency. | ai | |
| dependencies | unvetted-dep:@csszyx/svelte-adapter | AI (dependencies): Workspace sibling from the same csszyx monorepo; not an external untrusted dependency. | ai | |
| provenance | no-provenance | AI (provenance): Absence of Sigstore provenance is common; no other risk signals elevate this. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 0.9.10 | 10 / 9 | |
| 0.9.9 | 10 / 9 | |
| 0.9.8 | 10 / 9 | |
| 0.9.7 | 10 / 9 | |
| 0.9.6 | 10 / 9 | |
| 0.9.5 | 10 / 9 | |
| 0.9.4 | 10 / 9 | |
| 0.9.3 | 10 / 9 | |
| 0.9.2 | 10 / 9 | |
| 0.9.1 | 10 / 9 | |
| 0.9.0 | 8 / 8 | |
| 0.8.0 | 8 / 8 | |
| 0.7.0 | 8 / 8 | |
| 0.6.2 | 8 / 8 | |
| 0.6.0 | 8 / 8 | |
| 0.5.0 | 8 / 8 | |
| 0.4.0 | 8 / 8 | |
| 0.3.1 | 8 / 8 | |
| 0.3.0 | 8 / 8 | |
| 0.2.0 | 8 / 8 | |
| 0.1.3 | 8 / 8 | |
| 0.1.2 | 8 / 8 | |
| 0.1.1 | 8 / 8 | |
| 0.1.0 | 8 / 8 |
v0.9.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.