← Home

@xylabs/vitest-extended

100
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

xylabsdeprecatedshim

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@ariestools/vitest-extended AI (dependencies): Rename target of this deprecated shim package, not a novel unvetted dep. ai
provenance missing-githead AI (provenance): Trusted publisher (xyo) with 304 approved packages; isolated publish environment change, no other risk signals. ai
publish-pattern new-deps-added AI (publish-pattern): New dep is same-org xylabs package pinned to matching version; consistent with internal monorepo refactor. ai
provenance no-provenance AI (provenance): XY Labs packages consistently publish without Sigstore provenance; stable false positive for this org. ai

Versions (showing 100 of 132)

Version Deps Published
8.0.2 1 / 8
8.0.1 1 / 8
8.0.0 1 / 8
7.0.8 1 / 8
7.0.7 1 / 8
7.0.6 1 / 8
7.0.5 1 / 8
7.0.4 1 / 8
7.0.3 1 / 8
7.0.2 1 / 8
7.0.1 1 / 8
7.0.0 1 / 8
6.1.4 1 / 8
6.1.3 1 / 6
6.1.1 1 / 6
6.1.0 1 / 6
6.0.10 1 / 6
6.0.9 1 / 6
6.0.8 1 / 6
6.0.7 1 / 6
6.0.6 1 / 6
6.0.5 1 / 6
6.0.4 1 / 6
6.0.3 1 / 6
6.0.2 1 / 6
6.0.1 1 / 6
6.0.0 1 / 6
5.1.5 1 / 6
5.1.4 1 / 6
5.1.3 1 / 6
5.1.2 1 / 6
5.1.1 1 / 6
5.1.0 1 / 8
5.0.102 1 / 8
5.0.101 1 / 8
5.0.100 0 / 9
5.0.99 0 / 31
5.0.98 0 / 8
5.0.97 0 / 8
5.0.96 0 / 8
5.0.95 0 / 9
5.0.94 1 / 9
5.0.93 1 / 9
5.0.92 1 / 9
5.0.91 1 / 7
5.0.90 1 / 4
5.0.89 1 / 4
5.0.88 1 / 4
5.0.87 1 / 4
5.0.86 1 / 4
5.0.84 1 / 4
5.0.83 1 / 4
5.0.82 1 / 4
5.0.81 1 / 4
5.0.80 1 / 4
5.0.79 1 / 4
5.0.78 1 / 4
5.0.76 1 / 4
5.0.75 1 / 4
5.0.74 1 / 4
5.0.73 1 / 4
5.0.72 1 / 4
5.0.71 1 / 4
5.0.70 1 / 4
5.0.69 1 / 4
5.0.67 1 / 4
5.0.66 1 / 4
5.0.65 1 / 4
5.0.64 1 / 4
5.0.63 1 / 4
5.0.62 1 / 4
5.0.61 1 / 4
5.0.60 1 / 4
5.0.59 1 / 4
5.0.58 1 / 4
5.0.57 1 / 4
5.0.56 1 / 4
5.0.55 1 / 4
5.0.54 1 / 4
5.0.52 1 / 4
5.0.51 1 / 4
5.0.50 1 / 4
5.0.49 1 / 4
5.0.48 1 / 4
5.0.47 1 / 4
5.0.46 1 / 4
5.0.45 1 / 4
5.0.44 1 / 4
5.0.43 1 / 4
5.0.42 1 / 4
5.0.41 1 / 4
5.0.40 1 / 4
5.0.39 1 / 4
5.0.38 1 / 4
5.0.37 1 / 4
5.0.36 1 / 4
5.0.35 1 / 4
5.0.34 1 / 4
5.0.33 1 / 4
5.0.32 1 / 4
Showing 100 of 132 Next page →

v8.0.2

1 finding
INFO No provenance attestation provenance

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

v8.0.1

1 finding
INFO No provenance attestation provenance

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

v8.0.0

1 finding
INFO No provenance attestation provenance

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

v7.0.8

1 finding
INFO No provenance attestation provenance

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

v7.0.7

1 finding
INFO No provenance attestation provenance

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

v7.0.6

1 finding
INFO No provenance attestation provenance

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

v7.0.5

1 finding
INFO No provenance attestation provenance

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

v7.0.4

1 finding
INFO No provenance attestation provenance

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

v7.0.3

1 finding
INFO No provenance attestation provenance

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

v7.0.2

1 finding
INFO No provenance attestation provenance

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

v7.0.1

1 finding
INFO No provenance attestation provenance

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

v7.0.0

1 finding
INFO No provenance attestation provenance

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

v5.1.1

1 finding
INFO No provenance attestation provenance

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

v5.1.0

1 finding
INFO No provenance attestation provenance

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

v5.0.102

2 findings
INFO No provenance attestation provenance

[Accepted risk] 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.