@wippy-fe/theme
Theme variables, shared Tailwind config, and PrimeVue styling for Wippy web components.
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Internal scoped package from an org publisher; gitHead absence is a CI environment change, not a security signal for this package. | ai | |
| provenance | no-provenance | AI (provenance): Internal/private scoped package; provenance absence is expected and consistent across versions. | ai | |
| license | uncommon-license:UNLICENSED | AI (license): Scoped private package (@wippy-fe); UNLICENSED is intentional for internal use. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 0.0.46 | 2 / 0 | |
| 0.0.45 | 2 / 0 | |
| 0.0.44 | 2 / 0 | |
| 0.0.43 | 2 / 0 | |
| 0.0.42 | 2 / 0 | |
| 0.0.41 | 2 / 0 | |
| 0.0.40 | 2 / 0 | |
| 0.0.39 | 2 / 0 | |
| 0.0.38 | 2 / 0 | |
| 0.0.37 | 2 / 0 | |
| 0.0.36 | 2 / 0 | |
| 0.0.35 | 2 / 0 | |
| 0.0.34 | 2 / 0 | |
| 0.0.32 | 2 / 0 | |
| 0.0.31 | 2 / 0 | |
| 0.0.30 | 2 / 0 | |
| 0.0.29 | 2 / 0 | |
| 0.0.28 | 2 / 0 | |
| 0.0.27 | 2 / 0 | |
| 0.0.26 | 2 / 0 | |
| 0.0.25 | 2 / 0 | |
| 0.0.23 | 2 / 0 | |
| 0.0.22 | 2 / 0 | |
| 0.0.21 | 2 / 0 | |
| 0.0.20 | 2 / 0 | |
| 0.0.19 | 2 / 0 | |
| 0.0.18 | 2 / 0 | |
| 0.0.17 | 2 / 0 | |
| 0.0.16 | 2 / 0 | |
| 0.0.15 | 2 / 0 | |
| 0.0.14 | 2 / 0 | |
| 0.0.13 | 2 / 0 | |
| 0.0.12 | 2 / 0 | |
| 0.0.11 | 2 / 0 | |
| 0.0.10 | 2 / 0 | |
| 0.0.8 | 2 / 0 | |
| 0.0.7 | 2 / 0 |
v0.0.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.