@alfalab/core-components-bottom-sheet
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established monorepo package; provenance not used across the @alfalab suite. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-types | AI (dependencies): Sibling package in the same @alfalab monorepo; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-shared | AI (dependencies): Sibling package in the same @alfalab monorepo; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-backdrop | AI (dependencies): Sibling package in the same @alfalab monorepo; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-base-modal | AI (dependencies): Sibling package in the same @alfalab monorepo; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-navigation-bar-private | AI (dependencies): Sibling package in the same @alfalab monorepo; stable false positive for this package family. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 8.1.9 | 12 / 0 | |
| 8.1.8 | 12 / 0 | |
| 8.1.7 | 12 / 0 | |
| 8.1.6 | 12 / 0 | |
| 8.1.5 | 12 / 0 | |
| 8.1.4 | 12 / 0 | |
| 8.1.3 | 12 / 0 | |
| 8.1.2 | 12 / 0 | |
| 8.1.1 | 12 / 0 | |
| 8.1.0 | 12 / 0 | |
| 8.0.4 | 12 / 0 | |
| 8.0.3 | 12 / 0 | |
| 8.0.2 | 12 / 0 | |
| 8.0.1 | 12 / 0 | |
| 8.0.0 | 12 / 0 | |
| 7.4.5 | 12 / 0 | |
| 7.4.4 | 12 / 0 | |
| 7.4.3 | 12 / 0 | |
| 7.4.2 | 12 / 0 | |
| 7.4.1 | 12 / 0 | |
| 7.4.0 | 12 / 0 | |
| 7.3.1 | 12 / 0 | |
| 7.3.0 | 12 / 0 | |
| 7.2.1 | 12 / 0 | |
| 7.2.0 | 12 / 0 | |
| 7.1.0 | 12 / 0 | |
| 6.21.1 | 11 / 0 | |
| 6.21.0 | 11 / 0 | |
| 6.20.0 | 11 / 0 |
v8.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.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.
v7.4.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.
v7.3.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.
v7.3.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.
v7.2.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.
v7.2.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.
v7.1.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.
v6.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.21.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.
v6.20.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.