@asphalt-react/progress-bar
progress-bar
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): New publisher is a Gojek org account ([email protected]) with 3 approved packages; consistent with internal team rotation. | ai | |
| provenance | no-provenance | AI (provenance): Internal Gojek DLS package; provenance not configured for this org's publish pipeline. | ai | |
| license | uncommon-license:UNLICENSED | AI (license): Proprietary internal component; UNLICENSED is intentional for this package family. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 2.15.1 | 3 / 2 | |
| 2.15.0 | 3 / 2 | |
| 2.14.0 | 3 / 2 | |
| 2.13.0 | 3 / 2 | |
| 2.12.2 | 4 / 2 | |
| 2.12.1 | 4 / 2 | |
| 2.12.0 | 4 / 2 | |
| 2.11.0 | 4 / 2 | |
| 2.10.0 | 4 / 2 | |
| 2.9.0 | 4 / 2 | |
| 2.8.1 | 4 / 2 | |
| 2.8.0 | 4 / 2 | |
| 2.6.0 | 4 / 2 |
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.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.2
2 findingsThis version was published by a different npm account than previous versions on 2026-01-28. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.1
2 findingsThis version was published by a different npm account than previous versions on 2025-12-19. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.0
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 finding[Accepted risk] 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[Accepted risk] 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[Accepted risk] 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[Accepted risk] 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[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.