← Home

@xylabs/url

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): Deprecated shim intentionally re-exports the new sibling package @ariestools/sdk. ai
provenance missing-githead AI (provenance): Trusted xyo publisher with 530 approved packages; likely CI environment change rather than compromise. ai
publish-pattern dormant-publish AI (publish-pattern): Publisher xyo has 526 approved packages; dormancy likely reflects org release cadence, not takeover. ai

Versions (showing 51 of 131)

View all versions
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 / 9
7.0.1 0 / 9
7.0.0 0 / 9
6.1.4 0 / 9
6.1.3 0 / 7
6.1.1 0 / 7
6.1.0 0 / 7
6.0.10 0 / 7
6.0.9 0 / 7
6.0.8 0 / 7
6.0.7 0 / 7
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 / 5
5.0.89 0 / 5
5.0.88 0 / 5
5.0.87 0 / 5
5.0.86 0 / 5
5.0.84 0 / 5
5.0.83 0 / 5

v8.0.2

1 finding
LOW No provenance attestation provenance

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

v8.0.1

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

[Reject — re-review on republish] (prior reject: AI (publish-pattern): New dep @ariestools/sdk is the entire point of this version; cannot approve until that dep is vetted.) 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.

v8.0.0

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

[Reject — re-review on republish] (prior reject: AI (publish-pattern): New dep @ariestools/sdk is the entire point of this version; cannot approve until that dep is vetted.) 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.8

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

[Reject — re-review on republish] (prior reject: AI (publish-pattern): New dep @ariestools/sdk is the entire point of this version; cannot approve until that dep is vetted.) 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): New dep @ariestools/sdk is the entire point of this version; cannot approve until that dep is vetted.) 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): New dep @ariestools/sdk is the entire point of this version; cannot approve until that dep is vetted.) 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): New dep @ariestools/sdk is the entire point of this version; cannot approve until that dep is vetted.) 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): New dep @ariestools/sdk is the entire point of this version; cannot approve until that dep is vetted.) 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

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-07, known maintainer) provenance

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

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-05, known maintainer) provenance

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

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

1 finding
LOW No provenance attestation provenance

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

v5.0.96

1 finding
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.