@asphalt-react/appbar
Appbar
Supply chain provenance
Status for the latest visible version.
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
Keywords
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): Internal monorepo sibling dep; consistent pattern across all @asphalt-react packages. | ai | |
| dependencies | unvetted-dep:@asphalt-react/svg-normalizer | AI (dependencies): Internal monorepo sibling dep; consistent pattern across all @asphalt-react packages. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 2.15.0 | 6 / 2 | |
| 2.14.0 | 6 / 2 | |
| 2.12.2 | 7 / 2 | |
| 2.12.0 | 7 / 2 | |
| 2.8.0 | 7 / 2 | |
| 2.6.0 | 7 / 2 | |
| 2.5.0 | 7 / 2 | |
| 2.1.0 | 7 / 2 | |
| 2.0.2 | 7 / 2 | |
| 2.0.1 | 7 / 2 | |
| 2.0.0 | 7 / 2 |
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.