@asphalt-react/modal UNLICENSED 13 versions

@asphalt-react/modal

npm

Modal

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

asphaltmodalcomponentdlsdesign language system

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
license	uncommon-license:UNLICENSED	AI (license): Internal Gojek design system; UNLICENSED is intentional for proprietary internal packages.	ai	2026/05/14
phantom-deps	phantom-dep:@asphalt-react/stack	AI (phantom-deps): @asphalt-react/stack is a same-org sibling dep; phantom-dep heuristic is a stable false positive for this monorepo package.	ai	2026/05/14

Versions (showing 13 of 13)

Version	Deps	Published
2.15.1	8 / 2	2026-04-28
2.15.0	8 / 2	2026-04-13
2.14.0	8 / 2	2026-03-11
2.13.0	8 / 2	2026-02-19
2.12.2	9 / 2	2026-01-28
2.11.0	9 / 2	2025-11-10
2.10.0	9 / 2	2025-10-27
2.9.0	9 / 2	2025-10-02
2.8.1	9 / 2	2025-09-10
2.8.0	9 / 2	2025-08-14
2.6.0	9 / 2	2025-07-11
2.5.0	9 / 2	2025-06-03
2.4.0	9 / 2	2025-05-09

v2.15.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.14.0

1 finding

LOW No provenance attestation provenance

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

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.9.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.8.1

1 finding

LOW No provenance attestation provenance

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

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