@xyo-network/payloadset-plugins
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:node-screenlogic | AI (dependencies): Legit pool-automation witness plugin dependency matching new exports. | ai | |
| dependencies | unvetted-dep:es6-dynamic-template | AI (dependencies): Small templating util used by new plugin modules, benign. | ai | |
| dependencies | unvetted-dep:@xyo-network/uniswap-typechain | AI (dependencies): First-party XYO org package. | ai | |
| dependencies | unvetted-dep:@xyo-network/open-zeppelin-typechain | AI (dependencies): First-party XYO org package. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 7.2.0 | 31 / 36 | |
| 7.1.0 | 29 / 38 | |
| 7.0.4 | 1 / 78 | |
| 5.3.1 | 17 / 3 |
v7.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.