@asphalt-react/toggle-switch
Toggle Switch is like a physical switch for your apps that allows the users to turn things on or off
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 |
|---|---|---|---|---|
| license | uncommon-license:UNLICENSED | AI (license): Proprietary Gojek design system; UNLICENSED is intentional across all @asphalt-react packages. | ai | |
| provenance | no-provenance | AI (provenance): Gojek design system package; no provenance is consistent across all versions in this org. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 2.15.1 | 4 / 3 | |
| 2.15.0 | 4 / 3 | |
| 2.12.2 | 5 / 3 | |
| 2.12.1 | 5 / 3 | |
| 2.11.0 | 5 / 3 | |
| 2.10.0 | 5 / 3 | |
| 2.9.0 | 5 / 3 | |
| 2.8.1 | 5 / 3 | |
| 2.8.0 | 5 / 3 | |
| 2.6.0 | 5 / 3 | |
| 2.5.0 | 5 / 3 |
v2.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.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.
v2.6.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.
v2.5.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.