← Home

@xylabs/react-identicon

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): Sibling org package that this shim is explicitly deprecated in favor of. ai
publish-pattern new-deps-added AI (publish-pattern): Dependency swap matches documented deprecation/migration path. ai
provenance missing-githead AI (provenance): High-volume publisher xyo with strong approval history; isolated gitHead absence is not indicative of supply chain compromise for this package. ai
provenance publisher-changed AI (provenance): jonesmac is an established xylabs org publisher with 1331 approved packages; transition appears legitimate. ai

Versions (showing 36 of 36)

Version Deps Published
11.0.1 1 / 11
11.0.0 1 / 26
10.0.5 1 / 26
10.0.3 1 / 25
10.0.2 1 / 25
10.0.1 1 / 17
10.0.0 1 / 17
9.1.2 1 / 17
9.1.1 1 / 17
9.1.0 1 / 17
9.0.4 1 / 20
9.0.3 1 / 20
9.0.2 1 / 21
9.0.1 1 / 21
9.0.0 1 / 22
8.0.4 1 / 22
8.0.3 1 / 22
8.0.2 1 / 22
8.0.1 1 / 22
8.0.0 1 / 22
7.2.5 1 / 22
7.2.4 1 / 22
7.2.3 1 / 22
7.2.2 1 / 22
7.2.1 1 / 22
7.2.0 1 / 22
7.1.20 2 / 16
7.1.17 2 / 11
7.1.16 2 / 10
7.1.15 2 / 10
7.1.14 2 / 10
7.1.13 2 / 10
7.1.12 2 / 10
7.1.11 2 / 10
7.1.10 2 / 10
7.1.9 2 / 10

v11.0.1

1 finding
LOW No provenance attestation provenance

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

v11.0.0

1 finding
LOW No provenance attestation provenance

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

v10.0.5

1 finding
LOW No provenance attestation provenance

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

v10.0.3

1 finding
LOW No provenance attestation provenance

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

v10.0.2

1 finding
LOW No provenance attestation provenance

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

v10.0.1

1 finding
LOW No provenance attestation provenance

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

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