@xylabs/react-quick-tip-button
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/sdk-react | AI (dependencies): Sibling/successor package from same org per deprecation notice, not third-party. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Expected dep swap for deprecation shim pointing to its replacement package. | ai | |
| provenance | missing-githead | AI (provenance): XY Labs org with strong publisher track record; no material code changes; likely CI environment change. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from individual (jonesmac) to org account (xyo) is consistent with XY Labs consolidation; xyo has 961 approved packages. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by publisher account transition to org account; no malicious indicators present. | ai | |
| provenance | no-provenance | AI (provenance): XY Labs org consistently publishes without Sigstore provenance; stable pattern across 311 versions. | 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 | 1 / 23 | |
| 10.0.0 | 1 / 23 | |
| 9.1.2 | 1 / 23 | |
| 9.1.1 | 1 / 23 | |
| 9.1.0 | 1 / 23 | |
| 9.0.4 | 1 / 29 | |
| 9.0.3 | 1 / 29 | |
| 9.0.2 | 1 / 30 | |
| 9.0.1 | 1 / 30 | |
| 9.0.0 | 1 / 33 | |
| 8.0.4 | 1 / 33 | |
| 8.0.3 | 1 / 33 | |
| 8.0.2 | 1 / 33 | |
| 8.0.1 | 1 / 33 | |
| 8.0.0 | 1 / 33 | |
| 7.2.5 | 1 / 33 | |
| 7.2.4 | 1 / 33 | |
| 7.2.3 | 1 / 33 | |
| 7.2.2 | 1 / 33 | |
| 7.2.1 | 1 / 35 | |
| 7.2.0 | 1 / 35 | |
| 7.1.20 | 1 / 24 | |
| 7.1.17 | 1 / 15 | |
| 7.1.16 | 1 / 15 | |
| 7.1.15 | 1 / 15 | |
| 7.1.14 | 1 / 15 | |
| 7.1.13 | 1 / 15 | |
| 7.1.12 | 1 / 15 | |
| 7.1.11 | 1 / 14 | |
| 7.1.10 | 1 / 14 | |
| 7.1.9 | 1 / 14 |
v11.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
2 findings[Accepted risk] 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 (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.