@xylabs/object
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): @xylabs/zod is a first-party XYO Labs package pinned to the same version family; low risk for this publisher. | ai | |
| provenance | missing-githead | AI (provenance): High-volume publisher with clean track record; single missing gitHead in an otherwise unchanged release is low risk. | ai |
Versions (showing 23 of 123)
| Version | Deps | Published |
|---|---|---|
| 5.0.22 | 4 / 4 | |
| 5.0.21 | 4 / 4 | |
| 5.0.20 | 4 / 4 | |
| 5.0.19 | 4 / 4 | |
| 5.0.18 | 4 / 4 | |
| 5.0.17 | 4 / 4 | |
| 5.0.16 | 4 / 4 | |
| 5.0.15 | 4 / 4 | |
| 5.0.14 | 4 / 4 | |
| 5.0.13 | 4 / 4 | |
| 5.0.12 | 4 / 4 | |
| 5.0.11 | 4 / 4 | |
| 5.0.10 | 4 / 4 | |
| 5.0.9 | 4 / 4 | |
| 5.0.8 | 4 / 4 | |
| 5.0.7 | 4 / 4 | |
| 5.0.6 | 4 / 4 | |
| 5.0.5 | 4 / 4 | |
| 5.0.4 | 4 / 4 | |
| 5.0.3 | 4 / 4 | |
| 5.0.2 | 4 / 4 | |
| 5.0.1 | 4 / 4 | |
| 5.0.0 | 4 / 4 |
v5.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.