@zeedhi/zd-user-info-vue
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 |
|---|---|---|---|---|
| npm-metadata | url-dep:@zeedhi/zd-user-info-common | AI (npm-metadata): file: path in peerDependencies is a monorepo artifact; peer deps are not auto-installed, so no registry-bypass risk for consumers. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 3.1.0 | 0 / 13 | |
| 3.0.4 | 0 / 13 | |
| 3.0.3 | 0 / 13 | |
| 1.4.1 | 0 / 0 | |
| 1.4.0 | 0 / 0 | |
| 1.3.5 | 0 / 0 | |
| 1.3.4 | 0 / 0 | |
| 1.3.3 | 0 / 0 |
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.