@vue-skuilder/edit-ui
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo package; missing metadata is expected, not a spam/malware indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo component package; missing description is consistent across all versions. | ai | |
| phantom-deps | phantom-dep:vuetify | AI (phantom-deps): vuetify is a declared peerDependency used via config; phantom-dep false positive for this package. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 0.2.21 | 7 / 19 | |
| 0.2.20 | 7 / 19 | |
| 0.2.19 | 7 / 19 | |
| 0.2.18 | 7 / 19 | |
| 0.2.17 | 7 / 19 | |
| 0.2.16 | 7 / 19 | |
| 0.2.15 | 7 / 19 | |
| 0.2.14 | 7 / 19 | |
| 0.2.13 | 7 / 19 | |
| 0.2.12 | 7 / 19 | |
| 0.2.11 | 7 / 19 | |
| 0.2.10 | 7 / 19 | |
| 0.2.9 | 7 / 19 | |
| 0.2.8 | 7 / 19 | |
| 0.2.7 | 7 / 19 | |
| 0.2.5 | 7 / 19 | |
| 0.2.4 | 7 / 19 | |
| 0.2.3 | 7 / 19 | |
| 0.2.2 | 7 / 19 | |
| 0.2.1 | 7 / 19 | |
| 0.2.0 | 7 / 19 | |
| 0.1.40 | 7 / 19 | |
| 0.1.39 | 7 / 19 | |
| 0.1.38 | 7 / 19 | |
| 0.1.36 | 7 / 19 | |
| 0.1.35 | 7 / 19 | |
| 0.1.31 | 7 / 19 | |
| 0.1.30 | 7 / 19 | |
| 0.1.29 | 7 / 19 | |
| 0.1.28 | 7 / 19 | |
| 0.1.27 | 7 / 19 | |
| 0.1.26 | 7 / 19 | |
| 0.1.25 | 7 / 19 | |
| 0.1.24 | 7 / 19 | |
| 0.1.23 | 7 / 19 | |
| 0.1.22 | 7 / 19 | |
| 0.1.21 | 7 / 19 | |
| 0.1.20 | 7 / 19 | |
| 0.1.18 | 7 / 19 | |
| 0.1.17 | 7 / 19 | |
| 0.1.16 | 7 / 19 | |
| 0.1.15 | 7 / 19 | |
| 0.1.14 | 7 / 19 |
v0.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.