@duetds/react
This package includes React specific wrapper for Duet Design System Web Components.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): New publisher 'lahitapiola' matches the org identity in package.json author field; legitimate org account transition. | ai | |
| provenance | no-provenance | AI (provenance): Long-established package with consistent publishing history; lack of Sigstore attestation is not a risk signal here. | ai |
Versions (showing 58 of 58)
| Version | Deps | Published |
|---|---|---|
| 10.3.0 | 1 / 11 | |
| 10.2.4 | 1 / 11 | |
| 10.2.3 | 1 / 11 | |
| 10.2.2 | 1 / 11 | |
| 10.2.1 | 1 / 11 | |
| 10.2.0 | 1 / 11 | |
| 10.1.1 | 1 / 11 | |
| 10.1.0 | 1 / 11 | |
| 10.0.0 | 1 / 11 | |
| 9.20.0 | 1 / 11 | |
| 9.19.1 | 1 / 11 | |
| 9.19.0 | 1 / 11 | |
| 9.18.0 | 1 / 11 | |
| 9.17.0 | 1 / 11 | |
| 9.16.1 | 1 / 11 | |
| 9.16.0 | 1 / 11 | |
| 9.15.0 | 1 / 11 | |
| 9.14.0 | 1 / 11 | |
| 9.13.0 | 1 / 11 | |
| 9.12.2 | 1 / 11 | |
| 9.12.1 | 1 / 11 | |
| 9.12.0 | 1 / 11 | |
| 9.11.0 | 1 / 11 | |
| 9.10.0 | 1 / 11 | |
| 9.9.0 | 1 / 11 | |
| 9.8.1 | 1 / 11 | |
| 9.8.0 | 1 / 11 | |
| 9.7.3 | 1 / 11 | |
| 9.7.2 | 1 / 11 | |
| 9.7.1 | 1 / 11 | |
| 9.7.0 | 1 / 11 | |
| 9.6.0 | 1 / 11 | |
| 9.5.2 | 1 / 11 | |
| 9.5.1 | 1 / 11 | |
| 9.5.0 | 1 / 11 | |
| 9.4.2 | 1 / 11 | |
| 9.4.1 | 1 / 11 | |
| 9.4.0 | 1 / 11 | |
| 9.3.2 | 1 / 11 | |
| 9.3.1 | 1 / 11 | |
| 9.3.0 | 1 / 11 | |
| 9.2.10 | 1 / 11 | |
| 9.2.9 | 1 / 11 | |
| 9.2.8 | 1 / 11 | |
| 9.2.7 | 1 / 11 | |
| 9.2.6 | 1 / 11 | |
| 9.2.5 | 1 / 11 | |
| 9.2.4 | 1 / 11 | |
| 9.2.3 | 1 / 11 | |
| 9.2.2 | 1 / 11 | |
| 9.2.1 | 1 / 11 | |
| 9.2.0 | 1 / 11 | |
| 9.1.2 | 1 / 11 | |
| 9.1.1 | 1 / 11 | |
| 9.1.0 | 1 / 11 | |
| 9.0.2 | 1 / 11 | |
| 9.0.1 | 1 / 11 | |
| 9.0.0 | 1 / 11 |
v10.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.2
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 (lahitapiola) than the most recent previously approved version (kasimir-dka) on 2025-04-08, but lahitapiola 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.
v9.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.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 (lahitapiola) than the most recent previously approved version (kasimir-dka) on 2025-03-24, but lahitapiola 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.
v9.1.2
2 findingsThis version was published by a different npm account (kasimir-dka) than the most recent previously approved version (lahitapiola) on 2025-03-13. It has since remained available on npm for 491 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.1
2 findingsThis version was published by a different npm account (kasimir-dka) than the most recent previously approved version (lahitapiola) on 2025-03-06. It has since remained available on npm for 498 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.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 (lahitapiola) than the most recent previously approved version (gibasm) on 2025-02-20, but lahitapiola 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.
v9.0.2
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 (lahitapiola) than the most recent previously approved version (gibasm) on 2025-02-05, but lahitapiola 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.
v9.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.