@juzi/wechaty
Wechaty is a RPA SDK for Chatbot Makers.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
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 juzibot org fork; dormancy reflects infrequent release cadence, not account takeover indicators. | ai | |
| dependencies | unvetted-dep:file-box | AI (dependencies): Core wechaty file abstraction library; stable ecosystem dep. | ai | |
| dependencies | unvetted-dep:rx-queue | AI (dependencies): Wechaty-ecosystem queue utility; stable ecosystem dep. | ai | |
| dependencies | unvetted-dep:open-graph | AI (dependencies): Standard open-graph parsing lib; consistent with chatbot SDK use case. | ai | |
| dependencies | unvetted-dep:clone-class | AI (dependencies): Wechaty-ecosystem utility; stable ecosystem dep. | ai | |
| dependencies | unvetted-dep:gerror | AI (dependencies): Wechaty-ecosystem utility; consistent with package's documented dependency set. | ai | |
| dependencies | unvetted-dep:state-switch | AI (dependencies): Wechaty-ecosystem state machine utility; stable ecosystem dep. | ai | |
| dependencies | unvetted-dep:json-rpc-peer | AI (dependencies): JSON-RPC transport used by wechaty puppet service; stable ecosystem dep. | ai | |
| dependencies | unvetted-dep:wechaty-token | AI (dependencies): Wechaty-ecosystem token utility; stable ecosystem dep. | ai | |
| dependencies | unvetted-dep:@juzi/wechaty-puppet-service | AI (dependencies): Core juzibot puppet service; same publisher org, consistent with package purpose. | ai | |
| dependencies | unvetted-dep:memory-card | AI (dependencies): Wechaty-ecosystem storage utility; stable ecosystem dep. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 1.0.143 | 18 / 28 | |
| 1.0.142 | 18 / 28 | |
| 1.0.141 | 18 / 28 | |
| 1.0.138 | 18 / 28 | |
| 1.0.137 | 18 / 28 | |
| 1.0.136 | 18 / 28 | |
| 1.0.132 | 18 / 28 | |
| 1.0.128 | 18 / 28 | |
| 1.0.125 | 18 / 28 | |
| 1.0.122 | 18 / 28 | |
| 1.0.120 | 18 / 28 | |
| 1.0.118 | 18 / 28 | |
| 1.0.116 | 18 / 28 | |
| 1.0.115 | 18 / 28 | |
| 1.0.114 | 18 / 28 |
v1.0.142
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.141
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.138
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.137
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.136
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.132
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.128
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.125
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.122
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.120
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.118
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.116
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.115
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.114
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.