← Home

@asphalt-react/toggle-button

npm

ToggleButton

13
Versions
UNLICENSED
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

sayantan1211dawn29soorajjantoniomontanagoto.abhinavelayudhanira-gojekyessyprmtsr

Keywords

asphalttoggle-buttoncomponentdlsdesign language system

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@asphalt-react/context AI (dependencies): Sibling package in the same Gojek @asphalt-react monorepo; stable false positive. ai
license uncommon-license:UNLICENSED AI (license): Proprietary internal Gojek design-system component; UNLICENSED is intentional. ai
dependencies unvetted-dep:@asphalt-react/helper AI (dependencies): Sibling package in the same @asphalt-react org; stable false positive for this package family. ai
dependencies unvetted-dep:@asphalt-react/qualifier AI (dependencies): Sibling package in the same @asphalt-react org; stable false positive for this package family. ai
dependencies unvetted-dep:@asphalt-react/svg-normalizer AI (dependencies): Sibling package in the same @asphalt-react org; stable false positive for this package family. ai

Versions (showing 13 of 13)

Version Deps Published
2.15.1 5 / 3
2.14.0 5 / 3
2.13.0 5 / 3
2.12.1 6 / 3
2.12.0 6 / 3
2.11.0 6 / 3
2.10.0 6 / 3
2.9.0 6 / 3
2.8.1 6 / 3
2.8.0 6 / 3
2.6.0 6 / 3
2.5.0 6 / 3
2.4.0 6 / 3

v2.14.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.13.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.12.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.12.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.11.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.10.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.9.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.8.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.8.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.6.0

1 finding
LOW No provenance attestation provenance

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
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.