@alfalab/core-components-bank-card
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@alfalab/icons-logo | AI (dependencies): First-party @alfalab monorepo sibling; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@alfalab/icons-logotype | AI (dependencies): First-party @alfalab monorepo sibling; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-masked-input | AI (dependencies): First-party @alfalab monorepo sibling; stable pattern across all versions of this package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a well-known implicit TypeScript runtime dep; stable false positive for this package family. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 7.0.9 | 6 / 0 | |
| 7.0.8 | 6 / 0 | |
| 7.0.7 | 6 / 0 | |
| 7.0.6 | 6 / 0 | |
| 7.0.5 | 6 / 0 | |
| 7.0.4 | 6 / 0 | |
| 7.0.3 | 6 / 0 | |
| 7.0.2 | 6 / 0 | |
| 7.0.1 | 6 / 0 | |
| 7.0.0 | 6 / 0 | |
| 6.0.6 | 6 / 0 | |
| 6.0.5 | 6 / 0 | |
| 6.0.4 | 6 / 0 | |
| 5.8.22 | 6 / 0 |
v7.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.