@vant/weapp
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Established library with sporadic release cadence, not indicative of compromise. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Long-stale publisher change with no takedown; established pattern for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same historical maintainer transfer, publisher has clean 43/0 track record. | ai | |
| dependencies | unvetted-dep:@types/wechat-miniprogram | AI (dependencies): Official TypeScript types package for WeChat miniprogram; benign type-only dep. | ai | |
| phantom-deps | phantom-dep:@types/wechat-miniprogram | AI (phantom-deps): Types package used by convention/tooling, not direct import. | ai |
Versions (showing 51 of 83)
| Version | Deps | Published |
|---|---|---|
| 1.11.7 | 0 / 23 | |
| 1.11.6 | 0 / 21 | |
| 1.11.5 | 0 / 21 | |
| 1.11.4 | 0 / 21 | |
| 1.11.3 | 0 / 21 | |
| 1.11.2 | 0 / 21 | |
| 1.11.1 | 0 / 21 | |
| 1.11.0 | 0 / 21 | |
| 1.10.25 | 0 / 21 | |
| 1.10.24 | 0 / 21 | |
| 1.10.23 | 0 / 21 | |
| 1.10.22 | 0 / 21 | |
| 1.10.21 | 0 / 21 | |
| 1.10.20 | 0 / 21 | |
| 1.10.19 | 0 / 21 | |
| 1.10.18 | 0 / 21 | |
| 1.10.17 | 0 / 21 | |
| 1.10.16 | 0 / 21 | |
| 1.10.15 | 0 / 21 | |
| 1.10.14 | 0 / 21 | |
| 1.10.13 | 0 / 21 | |
| 1.10.12 | 0 / 21 | |
| 1.10.11 | 0 / 21 | |
| 1.10.10 | 0 / 21 | |
| 1.10.9 | 0 / 21 | |
| 1.10.8 | 0 / 21 | |
| 1.10.7 | 0 / 21 | |
| 1.10.6 | 0 / 21 | |
| 1.10.5 | 0 / 20 | |
| 1.10.4 | 0 / 20 | |
| 1.10.3 | 0 / 20 | |
| 1.10.2 | 0 / 21 | |
| 1.10.1 | 0 / 20 | |
| 1.10.0 | 0 / 20 | |
| 1.9.2 | 0 / 12 | |
| 1.9.1 | 0 / 12 | |
| 1.9.0 | 0 / 12 | |
| 1.8.7 | 0 / 12 | |
| 1.8.6 | 0 / 12 | |
| 1.8.5 | 0 / 12 | |
| 1.8.4 | 0 / 12 | |
| 1.8.3 | 0 / 12 | |
| 1.8.2 | 0 / 12 | |
| 1.8.1 | 0 / 12 | |
| 1.8.0 | 0 / 12 | |
| 1.7.2 | 0 / 12 | |
| 1.7.1 | 0 / 12 | |
| 1.7.0 | 0 / 12 | |
| 1.6.9 | 0 / 13 | |
| 1.6.8 | 0 / 42 | |
| 1.6.7 | 0 / 42 |
v1.11.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (landluck) than the most recent previously approved version (nemo-shen) on 2024-01-16, but landluck is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.11.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (landluck) than the most recent previously approved version (nemo-shen) on 2023-12-05, but landluck is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.11.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nemo-shen) than the most recent previously approved version (chenjiahan) on 2023-10-11, but nemo-shen is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.11.0
2 findingsThis version was published by a different npm account (landluck) than the most recent previously approved version (chenjiahan) on 2023-09-18. It has since remained available on npm for 1037 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.25
2 findingsThis version was published by a different npm account (landluck) than the most recent previously approved version (chenjiahan) on 2023-08-30. It has since remained available on npm for 1056 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.24
2 findingsThis version was published by a different npm account (landluck) than the most recent previously approved version (chenjiahan) on 2023-08-25. It has since remained available on npm for 1061 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.23
2 findingsThis version was published by a different npm account (landluck) than the most recent previously approved version (chenjiahan) on 2023-07-28. It has since remained available on npm for 1089 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.22
2 findingsThis version was published by a different npm account (landluck) than the most recent previously approved version (chenjiahan) on 2023-07-24. It has since remained available on npm for 1093 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.21
2 findingsThis version was published by a different npm account (landluck) than the most recent previously approved version (chenjiahan) on 2023-07-10. It has since remained available on npm for 1107 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.20
2 findingsThis version was published by a different npm account (landluck) than the most recent previously approved version (chenjiahan) on 2023-07-03. It has since remained available on npm for 1114 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.19
2 findingsThis version was published by a different npm account (landluck) than the most recent previously approved version (chenjiahan) on 2023-05-19. It has since remained available on npm for 1159 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.18
2 findingsThis version was published by a different npm account (landluck) than the most recent previously approved version (chenjiahan) on 2023-05-08. It has since remained available on npm for 1170 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.17
2 findingsThis version was published by a different npm account (landluck) than the most recent previously approved version (chenjiahan) on 2023-05-04. It has since remained available on npm for 1174 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.16
2 findingsThis version was published by a different npm account (landluck) than the most recent previously approved version (chenjiahan) on 2023-04-18. It has since remained available on npm for 1190 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.15
2 findingsThis version was published by a different npm account (landluck) than the most recent previously approved version (chenjiahan) on 2023-04-03. It has since remained available on npm for 1205 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.14
2 findingsThis version was published by a different npm account (landluck) than the most recent previously approved version (chenjiahan) on 2023-02-27. It has since remained available on npm for 1240 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.13
2 findingsThis version was published by a different npm account (landluck) than the most recent previously approved version (chenjiahan) on 2023-02-13. It has since remained available on npm for 1254 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.12
2 findingsThis version was published by a different npm account (landluck) than the most recent previously approved version (chenjiahan) on 2023-01-16. It has since remained available on npm for 1282 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.11
2 findingsThis version was published by a different npm account (landluck) than the most recent previously approved version (chenjiahan) on 2023-01-03. It has since remained available on npm for 1295 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.10
2 findingsThis version was published by a different npm account (landluck) than the most recent previously approved version (chenjiahan) on 2022-12-16. It has since remained available on npm for 1313 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.9
2 findingsThis version was published by a different npm account (landluck) than the most recent previously approved version (chenjiahan) on 2022-12-12. It has since remained available on npm for 1317 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.8
2 findingsThis version was published by a different npm account (landluck) than the most recent previously approved version (chenjiahan) on 2022-11-29. It has since remained available on npm for 1330 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.7
2 findingsThis version was published by a different npm account (landluck) than the most recent previously approved version (chenjiahan) on 2022-11-18. It has since remained available on npm for 1341 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.6
2 findingsThis version was published by a different npm account (landluck) than the most recent previously approved version (chenjiahan) on 2022-11-06. It has since remained available on npm for 1353 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (chenjiahan) than the most recent previously approved version (nemo-shen) on 2022-05-02, but chenjiahan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nemo-shen) than the most recent previously approved version (chenjiahan) on 2021-09-29, but nemo-shen is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.9.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nemo-shen) than the most recent previously approved version (chenjiahan) on 2021-09-27, but nemo-shen is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.8.7
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (chenjiahan) than the most recent previously approved version (nemo-shen) on 2021-09-22, but chenjiahan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nemo-shen) than the most recent previously approved version (chenjiahan) on 2021-08-30, but nemo-shen is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (chenjiahan) than the most recent previously approved version (rex-zsd) on 2021-08-18, but chenjiahan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.8.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (chenjiahan) than the most recent previously approved version (rex-zsd) on 2021-08-11, but chenjiahan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.7.2
2 findingsThis version was published by a different npm account (nemo-shen) than the most recent previously approved version (rex-zsd) on 2021-07-19. It has since remained available on npm for 1828 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
2 findingsThis version was published by a different npm account (nemo-shen) than the most recent previously approved version (rex-zsd) on 2021-07-06. It has since remained available on npm for 1841 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
2 findingsThis version was published by a different npm account (nemo-shen) than the most recent previously approved version (rex-zsd) on 2021-07-04. It has since remained available on npm for 1843 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.9
2 findingsThis version was published by a different npm account (nemo-shen) than the most recent previously approved version (rex-zsd) on 2021-06-06. It has since remained available on npm for 1871 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.