@xylabs/zod
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Manual publish by known maintainer; no source-commit link but no material change. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Routine maintainer-list churn within the XYO org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): atrouw is a pre-existing maintainer on prior approved versions. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Deprecation shim intentionally re-exports to @ariestools/sdk, the package's documented successor. | ai | |
| license | weak-copyleft-license:LGPL-3.0-only | AI (license): LGPL-3.0 is the declared license for this package family; stable across all versions. | ai | |
| typosquat | typosquat.levenshtein:koa | AI (typosquat): Scoped @xylabs package from XYOracleNetwork org; Levenshtein match to 'koa' is coincidental. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @xylabs package from XYOracleNetwork org; Levenshtein match to 'joi' is coincidental. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped @xylabs package from XYOracleNetwork org; Levenshtein match to 'got' is coincidental. | ai |
Versions (showing 51 of 90)
| Version | Deps | Published |
|---|---|---|
| 8.0.2 | 1 / 10 | |
| 8.0.1 | 1 / 10 | |
| 8.0.0 | 1 / 10 | |
| 7.0.6 | 1 / 10 | |
| 7.0.5 | 1 / 10 | |
| 7.0.4 | 1 / 10 | |
| 7.0.2 | 2 / 9 | |
| 7.0.1 | 2 / 9 | |
| 7.0.0 | 2 / 9 | |
| 6.1.4 | 2 / 9 | |
| 6.1.3 | 2 / 7 | |
| 6.1.1 | 2 / 7 | |
| 6.1.0 | 2 / 7 | |
| 6.0.10 | 2 / 7 | |
| 6.0.9 | 2 / 7 | |
| 6.0.8 | 2 / 7 | |
| 6.0.7 | 2 / 7 | |
| 6.0.6 | 2 / 7 | |
| 6.0.5 | 2 / 7 | |
| 6.0.4 | 2 / 7 | |
| 6.0.3 | 2 / 7 | |
| 6.0.2 | 2 / 7 | |
| 6.0.1 | 2 / 7 | |
| 6.0.0 | 2 / 7 | |
| 5.1.5 | 2 / 7 | |
| 5.1.4 | 2 / 7 | |
| 5.1.3 | 2 / 7 | |
| 5.1.2 | 2 / 7 | |
| 5.1.1 | 2 / 7 | |
| 5.1.0 | 2 / 9 | |
| 5.0.102 | 2 / 9 | |
| 5.0.101 | 2 / 9 | |
| 5.0.100 | 2 / 9 | |
| 5.0.99 | 2 / 31 | |
| 5.0.98 | 2 / 8 | |
| 5.0.97 | 2 / 8 | |
| 5.0.96 | 2 / 8 | |
| 5.0.95 | 2 / 9 | |
| 5.0.94 | 2 / 10 | |
| 5.0.93 | 2 / 10 | |
| 5.0.92 | 2 / 10 | |
| 5.0.91 | 2 / 8 | |
| 5.0.90 | 2 / 5 | |
| 5.0.89 | 2 / 5 | |
| 5.0.88 | 2 / 5 | |
| 5.0.87 | 2 / 5 | |
| 5.0.86 | 2 / 5 | |
| 5.0.84 | 2 / 5 | |
| 5.0.83 | 2 / 5 | |
| 5.0.82 | 2 / 5 | |
| 5.0.81 | 2 / 5 |
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
2 findings[Reject — re-review on republish] (prior reject: AI (publish-pattern): Replacing established @xylabs/* deps with unvetted @ariestools/sdk is a classic supply-chain pivot; generalizes to this version.) 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
1 findingPackage 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): Replacing established @xylabs/* deps with unvetted @ariestools/sdk is a classic supply-chain pivot; generalizes to this version.) 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): Replacing established @xylabs/* deps with unvetted @ariestools/sdk is a classic supply-chain pivot; generalizes to this version.) 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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
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 (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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.98
1 findingPackage 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.
v5.0.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.