← Home

@asphalt-react/slider

Slider

14
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

sayantan1211dawn29soorajjantoniomontanagoto.abhinavelayudhanira-gojekyessyprmtsr

Keywords

asphaltslidercomponentdlsdesign language system

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
license uncommon-license:UNLICENSED AI (license): Intentionally proprietary internal Gojek design system; UNLICENSED is expected across all @asphalt-react packages. ai
dependencies unvetted-dep:@asphalt-react/helper AI (dependencies): Internal sibling package from the same Gojek asphalt-react monorepo; not a third-party risk. ai
dependencies unvetted-dep:@asphalt-react/typography AI (dependencies): Internal sibling package from the same Gojek asphalt-react monorepo; not a third-party risk. ai

Versions (showing 14 of 14)

Version Deps Published
2.15.1 4 / 2
2.15.0 4 / 2
2.14.0 4 / 2
2.13.0 4 / 2
2.12.0 5 / 2
2.11.0 5 / 2
2.10.0 5 / 2
2.9.0 5 / 2
2.8.1 5 / 2
2.8.0 5 / 2
2.6.0 5 / 2
2.5.0 5 / 2
2.3.0 5 / 2
2.2.0 5 / 2

v2.3.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: goto.abhinav → elayudhanira-gojek (on 2025-04-11, known maintainer) provenance

This version was published by a different npm account (elayudhanira-gojek) than the most recent previously approved version (goto.abhinav) on 2025-04-11, but elayudhanira-gojek 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.

v2.2.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.