@asphalt-react/actionlist
Actionlist
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
asphaltactionlistcomponentdlsdesign language system
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@asphalt-react/helper | AI (dependencies): Sibling package in same @asphalt-react monorepo; expected unvetted status. | ai | |
| dependencies | unvetted-dep:@asphalt-react/context | AI (dependencies): Sibling package in same @asphalt-react monorepo; expected unvetted status. | ai | |
| dependencies | unvetted-dep:@asphalt-react/qualifier | AI (dependencies): Sibling package in same @asphalt-react monorepo; expected unvetted status. | ai | |
| provenance | no-provenance | AI (provenance): Gojek internal design system; no provenance is consistent across all versions of this package family. | ai | |
| license | uncommon-license:UNLICENSED | AI (license): Intentionally proprietary Gojek internal package; UNLICENSED is expected and stable. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 2.15.1 | 4 / 3 | |
| 2.15.0 | 4 / 3 | |
| 2.12.2 | 5 / 3 | |
| 2.12.1 | 5 / 3 | |
| 2.12.0 | 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.1.0 | 5 / 3 | |
| 2.0.1 | 5 / 3 | |
| 2.0.0 | 5 / 3 |
v2.1.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.