← Home

@xylabs/api

npm Repository Homepage
51
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

joelbcarterjordantrouwrphansen91jonesmacatrouw

Keywords

xylabsutilitytypescriptesm

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): Added dep is first-party @xylabs/fetch pinned to matching monorepo version, not an unvetted third party. ai
provenance missing-githead AI (provenance): Established publisher with 492 approvals; missing gitHead in one version is low risk given no code changes. ai
typosquat typosquat.levenshtein:hapi AI (typosquat): Scoped @xylabs package; Levenshtein match to 'hapi' is a false positive for this established org. ai
typosquat typosquat.levenshtein:pg AI (typosquat): Scoped @xylabs package; Levenshtein match to 'pg' is a false positive for this established org. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped @xylabs package; Levenshtein match to 'joi' is a false positive for this established org. ai
typosquat typosquat.levenshtein:ajv AI (typosquat): Scoped @xylabs package; Levenshtein match to 'ajv' is a false positive for this established org. ai

Versions (showing 51 of 130)

View all versions
Version Deps Published
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 3 / 9
7.0.1 3 / 9
7.0.0 3 / 9
6.1.4 3 / 9
6.1.3 3 / 7
6.1.1 3 / 7
6.1.0 3 / 7
6.0.10 3 / 7
6.0.9 3 / 7
6.0.8 3 / 7
6.0.7 3 / 8
6.0.6 3 / 8
6.0.5 3 / 8
6.0.4 3 / 8
6.0.3 3 / 8
6.0.2 3 / 8
6.0.1 3 / 8
6.0.0 3 / 8
5.1.5 3 / 8
5.1.4 3 / 8
5.1.3 3 / 8
5.1.2 3 / 8
5.1.1 3 / 7
5.1.0 3 / 9
5.0.102 3 / 9
5.0.101 3 / 9
5.0.100 3 / 9
5.0.99 3 / 31
5.0.98 3 / 8
5.0.97 3 / 8
5.0.96 3 / 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

v8.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.0.8

2 findings
HIGH New dependencies added: @ariestools/sdk publish-pattern

[Reject — re-review on republish] (prior reject: AI (publish-pattern): Replacing established xylabs deps with unknown @ariestools/sdk is a high-risk supply-chain substitution.) 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).

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.0.7

2 findings
HIGH New dependencies added: @ariestools/sdk publish-pattern

[Reject — re-review on republish] (prior reject: AI (publish-pattern): Replacing established xylabs deps with unknown @ariestools/sdk is a high-risk supply-chain substitution.) 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).

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.0.6

2 findings
HIGH New dependencies added: @ariestools/sdk publish-pattern

[Reject — re-review on republish] (prior reject: AI (publish-pattern): Replacing established xylabs deps with unknown @ariestools/sdk is a high-risk supply-chain substitution.) 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).

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.0.5

2 findings
HIGH New dependencies added: @ariestools/sdk publish-pattern

[Reject — re-review on republish] (prior reject: AI (publish-pattern): Replacing established xylabs deps with unknown @ariestools/sdk is a high-risk supply-chain substitution.) 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).

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.0.4

2 findings
HIGH New dependencies added: @ariestools/sdk publish-pattern

[Reject — re-review on republish] (prior reject: AI (publish-pattern): Replacing established xylabs deps with unknown @ariestools/sdk is a high-risk supply-chain substitution.) 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).

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.1.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.102

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: xyo → atrouw (on 2026-05-04, known maintainer) provenance

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 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.100

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.99

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.98

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.97

2 findings
HIGH New dependencies added: @xylabs/fetch publish-pattern

[Reject — re-review on republish] (prior reject: AI (publish-pattern): Replacing established xylabs deps with unknown @ariestools/sdk is a high-risk supply-chain substitution.) 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).

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.96

2 findings
HIGH New dependencies added: @xylabs/fetch publish-pattern

[Reject — re-review on republish] (prior reject: AI (publish-pattern): Replacing established xylabs deps with unknown @ariestools/sdk is a high-risk supply-chain substitution.) 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).

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.95

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.94

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[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.0.93

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[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.0.92

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[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.0.91

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[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.0.90

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[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.0.89

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.88

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.87

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.86

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.84

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.83

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.82

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.