@themeshift/vite-plugin-themeshift
Vite plugin that makes using Style Dictionary + SASS easy as pie.
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 0.4.0 | 1 / 7 | |
| 0.3.12 | 1 / 7 | |
| 0.3.11 | 1 / 5 | |
| 0.3.10 | 1 / 5 | |
| 0.3.9 | 1 / 5 | |
| 0.3.8 | 1 / 5 | |
| 0.3.7 | 1 / 5 | |
| 0.3.6 | 1 / 5 | |
| 0.3.5 | 1 / 5 | |
| 0.3.4 | 1 / 5 | |
| 0.3.3 | 1 / 5 | |
| 0.3.2 | 1 / 5 | |
| 0.3.1 | 1 / 5 | |
| 0.3.0 | 1 / 5 | |
| 0.2.7 | 1 / 5 | |
| 0.2.6 | 1 / 5 | |
| 0.2.5 | 1 / 5 | |
| 0.2.4 | 1 / 5 | |
| 0.2.3 | 1 / 5 | |
| 0.2.2 | 1 / 5 | |
| 0.2.1 | 1 / 5 |
v0.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.