@xyo-network/payload-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): Corresponds to new #pentair pool-control plugin module in this release. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Sparse README typical of internal monorepo sub-package, not spam. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Org account replaced by known individual maintainer; benign per provenance note. | ai | |
| provenance | missing-githead | AI (provenance): Manual publish by known maintainer explains missing gitHead; no behavior change. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer is a known email-matched account, not a takeover indicator. | ai | |
| dependencies | unvetted-dep:@xyo-network/elevation-payload-plugin | AI (dependencies): Same-org workspace sibling package, monorepo aggregator pattern. | ai | |
| dependencies | unvetted-dep:@xyo-network/url-safety-payload-plugin | AI (dependencies): Same-org workspace sibling package, monorepo aggregator pattern. | ai | |
| dependencies | unvetted-dep:@xyo-network/blockchain-payload-plugins | AI (dependencies): Same-org workspace sibling package, monorepo aggregator pattern. | ai | |
| dependencies | unvetted-dep:@xyo-network/image-thumbnail-payload-plugin | AI (dependencies): Same-org workspace sibling package, monorepo aggregator pattern. | ai | |
| dependencies | unvetted-dep:@xyo-network/module-instance-payload-plugin | AI (dependencies): Same-org workspace sibling package, monorepo aggregator pattern. | ai | |
| dependencies | unvetted-dep:@xyo-network/location-certainty-payload-plugin | AI (dependencies): Same-org workspace sibling package, monorepo aggregator pattern. | ai | |
| dependencies | unvetted-dep:@xyo-network/crypto-payload-plugins | AI (dependencies): Same-org workspace sibling package, monorepo aggregator pattern. | ai | |
| dependencies | unvetted-dep:@xyo-network/url-payload-plugin | AI (dependencies): Same-org workspace sibling package, monorepo aggregator pattern. | ai | |
| dependencies | unvetted-dep:@xyo-network/pentair-payload-plugin | AI (dependencies): Same-org workspace sibling package, monorepo aggregator pattern. | ai | |
| dependencies | unvetted-dep:@xyo-network/location-payload-plugin | AI (dependencies): Same-org workspace sibling package, monorepo aggregator pattern. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 7.2.0 | 8 / 12 | |
| 7.1.0 | 4 / 16 | |
| 7.0.4 | 0 / 34 | |
| 7.0.3 | 10 / 27 | |
| 7.0.2 | 10 / 27 | |
| 7.0.1 | 10 / 59 | |
| 7.0.0 | 10 / 59 | |
| 6.1.0 | 10 / 60 | |
| 6.0.3 | 10 / 62 | |
| 6.0.2 | 10 / 63 | |
| 6.0.1 | 10 / 84 | |
| 6.0.0 | 10 / 87 | |
| 5.5.2 | 10 / 87 | |
| 5.5.1 | 10 / 87 | |
| 5.5.0 | 10 / 89 | |
| 5.4.10 | 10 / 90 | |
| 5.4.9 | 10 / 90 | |
| 5.4.7 | 10 / 100 | |
| 5.4.6 | 10 / 100 | |
| 5.4.5 | 10 / 100 | |
| 5.4.4 | 10 / 67 | |
| 5.4.3 | 10 / 67 | |
| 5.4.2 | 10 / 67 | |
| 5.4.1 | 10 / 70 | |
| 5.4.0 | 10 / 70 | |
| 5.3.4 | 10 / 53 | |
| 5.3.3 | 10 / 53 | |
| 5.3.2 | 0 / 62 | |
| 5.3.1 | 11 / 3 |
v7.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
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.
v7.0.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
v7.0.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
v7.0.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (atrouw) than the most recent previously approved version (xyo) on 2026-05-05, but atrouw is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.5
3 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
This version was published by a different npm account (xyo) than the most recent previously approved version (joelbcarter) on 2026-04-06, but xyo 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.
v5.4.4
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: joelbcarter.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (joelbcarter) than the most recent previously approved version (xyo) on 2026-04-06, but joelbcarter 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.
v5.4.3
3 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: joelbcarter.
This version was published by a different npm account (joelbcarter) than the most recent previously approved version (xyo) on 2026-04-03, but joelbcarter 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.
v5.4.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
v5.4.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
v5.4.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
v5.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.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 (xyo) than the most recent previously approved version (joelbcarter) on 2026-03-31, but xyo 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.
v5.3.2
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.