@vnejs/plugins.core.storage
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 plugin; sparse metadata is expected for org-internal packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal package; missing description is consistent across vnejs monorepo packages. | ai | |
| provenance | no-provenance | AI (provenance): vnejs monorepo does not use Sigstore provenance; stable pattern across versions. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.2.0 | 2 / 3 | |
| 0.1.19 | 2 / 3 | |
| 0.1.18 | 2 / 3 | |
| 0.1.17 | 2 / 3 | |
| 0.1.16 | 2 / 1 | |
| 0.1.15 | 2 / 1 | |
| 0.1.14 | 2 / 1 | |
| 0.1.13 | 2 / 1 | |
| 0.1.12 | 2 / 1 | |
| 0.1.11 | 2 / 1 | |
| 0.1.10 | 2 / 1 | |
| 0.1.9 | 2 / 1 | |
| 0.1.8 | 2 / 1 | |
| 0.1.7 | 2 / 1 | |
| 0.1.6 | 2 / 1 | |
| 0.1.5 | 1 / 0 | |
| 0.1.4 | 1 / 0 | |
| 0.1.3 | 1 / 0 | |
| 0.1.2 | 1 / 0 | |
| 0.1.1 | 1 / 0 | |
| 0.1.0 | 1 / 0 | |
| 0.0.1 | 1 / 0 |
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.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.