@xylabs/react-common
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@xylabs/react-base-page | AI (phantom-deps): Same-org monorepo re-export pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@xylabs/react-portal | AI (phantom-deps): Same-org monorepo re-export pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@xylabs/react-select | AI (phantom-deps): Same-org monorepo re-export pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@xylabs/react-flexbox | AI (phantom-deps): Same-org monorepo re-export pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@xylabs/react-error | AI (phantom-deps): Same-org monorepo re-export pattern; stable false positive for this package. | ai | |
| provenance | publisher-changed | AI (provenance): xyo is the XY Labs org account with 3410 approved packages; transition from individual to org account is expected for this namespace. | ai | |
| dependencies | unvetted-dep:@xylabs/react-base-page | AI (dependencies): Same-org sibling dep released in lockstep; consistent with XY Labs monorepo release pattern. | ai | |
| dependencies | unvetted-dep:@xylabs/react-portal | AI (dependencies): Same-org sibling dep released in lockstep; consistent with XY Labs monorepo release pattern. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 8.0.1 | 5 / 36 | |
| 7.1.20 | 7 / 28 | |
| 7.1.17 | 6 / 14 | |
| 7.1.16 | 6 / 13 | |
| 7.1.15 | 6 / 13 | |
| 7.1.14 | 6 / 13 | |
| 7.1.13 | 6 / 13 | |
| 7.1.12 | 6 / 13 | |
| 7.1.11 | 7 / 13 | |
| 7.1.10 | 7 / 13 | |
| 7.1.9 | 7 / 13 |
v8.0.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: atrouw.
Package 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-13, 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.
v7.1.20
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: xyo.
This version was published by a different npm account than previous versions on 2026-04-07. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.17
2 findingsThis version was published by a different npm account than previous versions on 2026-03-09. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.