@xylabs/platform
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): atrouw is a known maintainer matched by email per provenance INFO finding. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Team-internal maintainer list change, no behavioral change in package. | ai | |
| provenance | missing-githead | AI (provenance): Manual publish by known maintainer; no code diff vs prior approved version. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Deprecation shim redirecting to renamed sibling package under same org, matches stated intent. | ai | |
| license | weak-copyleft-license:LGPL-3.0-only | AI (license): LGPL-3.0-only is the declared license for this package across all versions; stable false positive. | ai |
Versions (showing 51 of 131)
| Version | Deps | Published |
|---|---|---|
| 8.0.2 | 1 / 10 | |
| 8.0.1 | 1 / 10 | |
| 8.0.0 | 1 / 10 | |
| 7.0.8 | 1 / 10 | |
| 7.0.7 | 1 / 10 | |
| 7.0.6 | 1 / 10 | |
| 7.0.5 | 1 / 10 | |
| 7.0.4 | 1 / 10 | |
| 7.0.2 | 0 / 10 | |
| 7.0.1 | 0 / 10 | |
| 7.0.0 | 0 / 10 | |
| 6.1.4 | 0 / 10 | |
| 6.1.3 | 0 / 8 | |
| 6.1.1 | 0 / 8 | |
| 6.1.0 | 0 / 8 | |
| 6.0.10 | 0 / 8 | |
| 6.0.9 | 0 / 8 | |
| 6.0.8 | 0 / 8 | |
| 6.0.7 | 0 / 8 | |
| 6.0.6 | 0 / 7 | |
| 6.0.5 | 0 / 7 | |
| 6.0.4 | 0 / 7 | |
| 6.0.3 | 0 / 7 | |
| 6.0.2 | 0 / 7 | |
| 6.0.1 | 0 / 7 | |
| 6.0.0 | 0 / 7 | |
| 5.1.5 | 0 / 7 | |
| 5.1.4 | 0 / 7 | |
| 5.1.3 | 0 / 7 | |
| 5.1.2 | 0 / 7 | |
| 5.1.1 | 0 / 6 | |
| 5.1.0 | 0 / 8 | |
| 5.0.102 | 0 / 8 | |
| 5.0.101 | 0 / 8 | |
| 5.0.100 | 0 / 8 | |
| 5.0.99 | 0 / 30 | |
| 5.0.98 | 0 / 7 | |
| 5.0.97 | 0 / 7 | |
| 5.0.96 | 0 / 7 | |
| 5.0.95 | 0 / 8 | |
| 5.0.94 | 0 / 9 | |
| 5.0.93 | 0 / 9 | |
| 5.0.92 | 0 / 9 | |
| 5.0.91 | 0 / 7 | |
| 5.0.90 | 0 / 4 | |
| 5.0.89 | 0 / 4 | |
| 5.0.88 | 0 / 4 | |
| 5.0.87 | 0 / 4 | |
| 5.0.86 | 0 / 4 | |
| 5.0.84 | 0 / 4 | |
| 5.0.83 | 0 / 4 |
v8.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.8
2 findings[Reject — re-review on republish] (prior reject: AI (publish-pattern): Adding @ariestools/sdk as sole runtime dep while deprecating the package in its favor is a high-risk supply-chain pattern.) This version introduces 1 new runtime dependency(ies) compared to the last vetted version. New dependencies on established packages warrant extra scrutiny — this was the axios attack vector (adding plain-crypto-js).
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.7
2 findings[Reject — re-review on republish] (prior reject: AI (publish-pattern): Adding @ariestools/sdk as sole runtime dep while deprecating the package in its favor is a high-risk supply-chain pattern.) This version introduces 1 new runtime dependency(ies) compared to the last vetted version. New dependencies on established packages warrant extra scrutiny — this was the axios attack vector (adding plain-crypto-js).
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.6
2 findings[Reject — re-review on republish] (prior reject: AI (publish-pattern): Adding @ariestools/sdk as sole runtime dep while deprecating the package in its favor is a high-risk supply-chain pattern.) This version introduces 1 new runtime dependency(ies) compared to the last vetted version. New dependencies on established packages warrant extra scrutiny — this was the axios attack vector (adding plain-crypto-js).
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.5
2 findings[Reject — re-review on republish] (prior reject: AI (publish-pattern): Adding @ariestools/sdk as sole runtime dep while deprecating the package in its favor is a high-risk supply-chain pattern.) This version introduces 1 new runtime dependency(ies) compared to the last vetted version. New dependencies on established packages warrant extra scrutiny — this was the axios attack vector (adding plain-crypto-js).
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
2 findings[Reject — re-review on republish] (prior reject: AI (publish-pattern): Adding @ariestools/sdk as sole runtime dep while deprecating the package in its favor is a high-risk supply-chain pattern.) This version introduces 1 new runtime dependency(ies) compared to the last vetted version. New dependencies on established packages warrant extra scrutiny — this was the axios attack vector (adding plain-crypto-js).
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.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-19, 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.1.5
2 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.
v5.1.4
2 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.
v5.1.3
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-14, 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.1.2
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-07, 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.1.1
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.1.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-04, 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.0.102
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-04, 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.0.101
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.100
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.99
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.98
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.97
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.96
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.95
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.94
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.93
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.92
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.91
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.90
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.