← Home

@tarojs/plugin-platform-weapp

npm Repository Homepage

微信小程序平台插件

30
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

yuchexuanzebindefaultleedrchankyjoqq592743779advancedcatbaosiqingzakaryliuzejiavasily.cjjhardenzheng2

Keywords

taro

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): New dep is a same-version first-party sibling within the Taro monorepo; not a third-party supply-chain risk. ai
dependencies unvetted-dep:@tarojs/service AI (dependencies): @tarojs/service is a first-party Taro monorepo package; version-pinned to match this package's own version. ai

Versions (showing 30 of 30)

Version Deps Published
4.2.1 0 / 3
4.2.0 0 / 3
4.1.11 0 / 3
4.1.10 0 / 3
4.1.9 0 / 3
4.1.8 0 / 3
4.1.7 0 / 3
4.1.6 0 / 3
4.1.5 0 / 3
4.1.4 0 / 3
4.1.3 0 / 3
4.1.2 0 / 3
4.1.1 0 / 3
4.1.0 0 / 3
4.0.13 0 / 3
4.0.12 0 / 3
4.0.11 0 / 3
4.0.10 0 / 3
4.0.9 0 / 3
4.0.8 0 / 3
4.0.7 0 / 3
4.0.6 0 / 3
4.0.5 0 / 3
4.0.4 0 / 3
4.0.3 0 / 3
4.0.2 0 / 3
4.0.1 1 / 5
4.0.0 0 / 3
3.6.40 1 / 5
3.6.39 1 / 5

v4.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.1

1 finding
LOW No provenance attestation provenance

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
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.