@xylabs/sdk-js
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): The added dep @xylabs/sdk is the intentional redirect target per the package's deprecation notice. | ai | |
| dependencies | unvetted-dep:@xylabs/sdk | AI (dependencies): Package is explicitly a re-export shim for @xylabs/sdk; this dep is its entire stated purpose. | ai | |
| dependencies | unvetted-dep:@xylabs/ellipsize | AI (dependencies): First-party @xylabs/* dep consistent with the rest of the SDK's dependency set; low risk. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): xyo removal paired with atrouw addition reflects a known maintainer rotation, not a hostile takeover. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): atrouw is a known maintainer matched by email on prior approved versions; not a new external actor. | ai | |
| dependencies | unvetted-dep:@xylabs/log | AI (dependencies): Same xylabs org namespace as all other deps; consistent with the package's established ecosystem pattern. | ai | |
| provenance | no-provenance | AI (provenance): Established XY Labs monorepo package; lack of provenance is consistent across all versions. | 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; not a security concern. | ai |
Versions (showing 51 of 124)
| 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.3 | 1 / 10 | |
| 7.0.2 | 1 / 10 | |
| 7.0.1 | 1 / 10 | |
| 7.0.0 | 1 / 10 | |
| 6.1.4 | 32 / 10 | |
| 6.1.3 | 32 / 8 | |
| 6.1.1 | 32 / 8 | |
| 6.1.0 | 31 / 8 | |
| 6.0.10 | 34 / 11 | |
| 6.0.9 | 34 / 11 | |
| 6.0.8 | 34 / 11 | |
| 6.0.7 | 34 / 12 | |
| 6.0.6 | 34 / 12 | |
| 6.0.5 | 34 / 12 | |
| 6.0.3 | 34 / 12 | |
| 6.0.0 | 34 / 13 | |
| 5.1.5 | 34 / 13 | |
| 5.1.4 | 34 / 13 | |
| 5.1.3 | 34 / 13 | |
| 5.1.2 | 34 / 13 | |
| 5.1.1 | 34 / 13 | |
| 5.1.0 | 34 / 14 | |
| 5.0.102 | 35 / 15 | |
| 5.0.101 | 35 / 15 | |
| 5.0.100 | 35 / 15 | |
| 5.0.99 | 35 / 36 | |
| 5.0.98 | 35 / 9 | |
| 5.0.97 | 35 / 7 | |
| 5.0.96 | 35 / 7 | |
| 5.0.94 | 36 / 10 | |
| 5.0.90 | 35 / 4 | |
| 5.0.89 | 35 / 4 | |
| 5.0.88 | 35 / 4 | |
| 5.0.87 | 35 / 4 | |
| 5.0.86 | 35 / 4 | |
| 5.0.84 | 35 / 4 | |
| 5.0.83 | 35 / 4 | |
| 5.0.82 | 35 / 4 | |
| 5.0.81 | 35 / 4 | |
| 5.0.80 | 35 / 5 | |
| 5.0.79 | 34 / 4 | |
| 5.0.78 | 34 / 4 | |
| 5.0.76 | 34 / 5 |
v8.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
2 findings[Accepted risk] 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
2 findings[Accepted risk] 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.