@nova-design-system/nova-vue
Nova is a design system created by Elia Group to empower creators to efficiently build solutions that people love to use.
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 | publisher-changed | AI (provenance): Transition to GitHub Actions publisher is consistent with CI/CD automation for this org-scoped design system package. | ai | |
| provenance | no-provenance | AI (provenance): CI-published design system package; provenance absence is common and not a risk signal here. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 3.35.0 | 2 / 3 | |
| 3.34.0 | 2 / 3 | |
| 3.33.0 | 2 / 3 | |
| 3.32.0 | 2 / 3 | |
| 3.31.1 | 2 / 3 | |
| 3.31.0 | 2 / 3 | |
| 3.30.0 | 2 / 3 | |
| 3.29.0 | 2 / 3 | |
| 3.28.0 | 2 / 3 | |
| 3.27.0 | 2 / 3 | |
| 3.26.0 | 2 / 3 | |
| 3.25.0 | 2 / 3 | |
| 3.24.0 | 2 / 3 | |
| 3.23.0 | 2 / 3 | |
| 3.22.0 | 2 / 3 | |
| 3.21.0 | 2 / 3 | |
| 3.20.0 | 2 / 3 | |
| 3.19.0 | 2 / 3 | |
| 3.18.0 | 2 / 3 | |
| 3.17.0 | 2 / 3 | |
| 3.16.0 | 2 / 3 | |
| 3.15.0 | 1 / 3 | |
| 3.14.0 | 1 / 3 | |
| 3.13.0 | 1 / 3 | |
| 3.12.0 | 1 / 3 | |
| 3.11.0 | 0 / 4 | |
| 3.10.0 | 0 / 4 | |
| 3.9.1 | 0 / 4 | |
| 3.9.0 | 0 / 4 | |
| 3.8.0 | 0 / 4 | |
| 3.7.0 | 0 / 4 | |
| 3.6.0 | 0 / 4 | |
| 3.5.0 | 0 / 4 | |
| 3.4.0 | 0 / 4 | |
| 3.3.0 | 0 / 4 | |
| 3.2.0 | 0 / 4 | |
| 3.1.0 | 0 / 4 | |
| 3.0.0 | 0 / 4 |
v3.35.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.34.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.33.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.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.