← Home

@xylabs/react-pixel-debugger

36
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

utilitytypescriptreact

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@ariestools/sdk-react AI (dependencies): New name for consolidated first-party sdk-react dependency; shim package deprecation is legitimate. ai
publish-pattern new-deps-added AI (publish-pattern): @mui/material is a well-established, widely-used UI library; not a suspicious dependency for a React UI package. ai
provenance publisher-changed AI (provenance): jonesmac is an established xylabs org publisher with 3589 approved packages; transition appears legitimate. ai
provenance no-provenance AI (provenance): Consistent across all @xylabs/* packages; org does not use Sigstore attestation. ai

Versions (showing 36 of 36)

Version Deps Published
11.0.1 1 / 14
11.0.0 1 / 29
10.0.5 1 / 29
10.0.3 1 / 28
10.0.2 1 / 28
10.0.1 5 / 21
10.0.0 5 / 21
9.1.2 5 / 21
9.1.1 5 / 21
9.1.0 5 / 21
9.0.4 5 / 27
9.0.3 5 / 27
9.0.2 5 / 28
9.0.1 5 / 28
9.0.0 5 / 31
8.0.4 5 / 31
8.0.3 5 / 31
8.0.2 5 / 31
8.0.1 5 / 31
8.0.0 5 / 31
7.2.5 5 / 31
7.2.4 5 / 31
7.2.3 5 / 31
7.2.2 5 / 31
7.2.1 5 / 33
7.2.0 5 / 33
7.1.20 6 / 23
7.1.17 6 / 15
7.1.16 6 / 14
7.1.15 6 / 14
7.1.14 6 / 14
7.1.13 6 / 14
7.1.12 6 / 14
7.1.11 6 / 13
7.1.10 6 / 13
7.1.9 6 / 13

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

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

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

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

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

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

v10.0.0

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: jonesmac → atrouw (on 2026-06-30, known maintainer) provenance

This version was published by a different npm account (atrouw) than the most recent previously approved version (jonesmac) on 2026-06-30, but atrouw is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.