vant
Mobile UI Components built on 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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Long-standing monorepo maintainer roster changes, no new suspicious publisher. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @vue/shared is an official Vue.js org package, benign addition. | ai | |
| dependencies | unvetted-dep:@vant/use | AI (dependencies): @vant/use is a first-party Vant ecosystem package maintained by the same author (chenjiahan/vant-ui org); stable dependency for this package. | ai | |
| dependencies | unvetted-dep:@vant/popperjs | AI (dependencies): @vant/popperjs is a first-party Vant ecosystem package maintained by the same author (chenjiahan/vant-ui org); stable dependency for this package. | ai | |
| provenance | no-provenance | AI (provenance): Vant is a well-established library; lack of Sigstore provenance is common and not a security concern given the publisher's track record. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 4.10.0 | 3 / 18 | |
| 4.9.24 | 3 / 19 | |
| 4.9.23 | 3 / 19 | |
| 4.9.22 | 3 / 19 | |
| 4.9.21 | 3 / 19 | |
| 4.0.11 | 2 / 11 | |
| 4.0.10 | 2 / 11 | |
| 4.0.9 | 2 / 11 | |
| 4.0.8 | 2 / 11 | |
| 4.0.7 | 2 / 11 | |
| 4.0.6 | 2 / 11 | |
| 4.0.5 | 2 / 11 | |
| 4.0.4 | 2 / 11 | |
| 4.0.3 | 2 / 11 | |
| 4.0.2 | 2 / 11 | |
| 4.0.1 | 2 / 11 | |
| 4.0.0 | 2 / 11 |
v4.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.22
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: chenjiahan.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.21
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: chenjiahan.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.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.
v4.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.