@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, 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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Metadata-only regression, no behavioral change; consistent with established org's publish pipeline. | ai | |
| dependencies | unvetted-dep:@ariestools/sdk-react | AI (dependencies): Sibling/successor package under same org's rebrand, consistent with deprecation notice. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Dep is the org's own successor SDK per deprecation notice, not an unrelated third party. | 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-base-page | 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-error | 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 | |
| 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-portal | AI (dependencies): Same-org sibling dep released in lockstep; consistent with XY Labs monorepo release pattern. | 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 |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 11.0.0 | 1 / 29 | |
| 10.0.5 | 1 / 29 | |
| 10.0.3 | 1 / 28 | |
| 10.0.2 | 1 / 28 | |
| 10.0.1 | 5 / 23 | |
| 10.0.0 | 5 / 23 | |
| 9.1.2 | 5 / 23 | |
| 9.1.1 | 5 / 23 | |
| 9.1.0 | 5 / 23 | |
| 9.0.4 | 5 / 31 | |
| 9.0.3 | 5 / 31 | |
| 9.0.2 | 5 / 30 | |
| 9.0.1 | 5 / 32 | |
| 9.0.0 | 5 / 35 | |
| 8.0.4 | 5 / 35 | |
| 8.0.3 | 5 / 35 | |
| 8.0.2 | 5 / 36 | |
| 8.0.1 | 5 / 36 | |
| 8.0.0 | 5 / 36 | |
| 7.2.5 | 5 / 36 | |
| 7.2.4 | 5 / 36 | |
| 7.2.3 | 5 / 36 | |
| 7.2.2 | 5 / 36 | |
| 7.2.1 | 5 / 38 | |
| 7.2.0 | 5 / 38 | |
| 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 |
v11.0.0
2 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.
v10.0.5
2 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.
v10.0.3
2 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.
v10.0.2
2 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.
v10.0.1
2 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.
v10.0.0
2 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.
v9.0.0
2 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.
v8.0.3
2 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.
v8.0.2
2 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.
v8.0.0
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: jonesmac.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jonesmac) than the most recent previously approved version (xyo) on 2026-05-07, but jonesmac 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.
v7.2.5
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-07, 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.2.4
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-07, 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.2.3
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-05, 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.2.2
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-05, 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.2.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-05, 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.2.0
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-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.