@xylabs/vitest-matchers
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@ariestools/vitest-matchers | AI (dependencies): Sibling package under same publisher; shim explicitly re-exports it. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Expected: package intentionally converted to a thin re-export shim. | 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; stable false positive. | ai |
Versions (showing 51 of 127)
| Version | Deps | Published |
|---|---|---|
| 8.0.2 | 1 / 6 | |
| 8.0.1 | 1 / 6 | |
| 8.0.0 | 1 / 6 | |
| 7.0.8 | 0 / 8 | |
| 7.0.7 | 0 / 8 | |
| 7.0.6 | 0 / 8 | |
| 7.0.5 | 0 / 8 | |
| 7.0.4 | 0 / 8 | |
| 7.0.3 | 0 / 8 | |
| 7.0.2 | 0 / 8 | |
| 7.0.1 | 0 / 8 | |
| 7.0.0 | 0 / 8 | |
| 6.1.4 | 0 / 8 | |
| 6.1.3 | 0 / 6 | |
| 6.1.1 | 0 / 6 | |
| 6.1.0 | 0 / 6 | |
| 6.0.10 | 0 / 6 | |
| 6.0.9 | 0 / 6 | |
| 6.0.8 | 0 / 6 | |
| 6.0.7 | 0 / 6 | |
| 6.0.6 | 0 / 6 | |
| 6.0.5 | 0 / 6 | |
| 6.0.4 | 0 / 6 | |
| 6.0.3 | 0 / 6 | |
| 6.0.2 | 0 / 6 | |
| 6.0.1 | 0 / 6 | |
| 6.0.0 | 0 / 6 | |
| 5.1.5 | 0 / 6 | |
| 5.1.4 | 0 / 6 | |
| 5.1.3 | 0 / 6 | |
| 5.1.2 | 0 / 6 | |
| 5.1.1 | 0 / 6 | |
| 5.1.0 | 0 / 7 | |
| 5.0.102 | 0 / 7 | |
| 5.0.101 | 0 / 7 | |
| 5.0.100 | 0 / 7 | |
| 5.0.99 | 0 / 29 | |
| 5.0.98 | 0 / 6 | |
| 5.0.97 | 0 / 5 | |
| 5.0.96 | 0 / 5 | |
| 5.0.90 | 0 / 3 | |
| 5.0.89 | 0 / 3 | |
| 5.0.88 | 0 / 3 | |
| 5.0.87 | 0 / 3 | |
| 5.0.86 | 0 / 3 | |
| 5.0.84 | 0 / 3 | |
| 5.0.83 | 0 / 3 | |
| 5.0.82 | 0 / 3 | |
| 5.0.81 | 0 / 3 | |
| 5.0.80 | 0 / 3 | |
| 5.0.79 | 0 / 3 |
v8.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
2 findingsPackage 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 findingsPackage 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.