@alfalab/core-components-universal-modal
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/core-components-shared | AI (dependencies): Internal sibling dep from the same @alfalab/core-components monorepo; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-mq | AI (dependencies): Internal sibling dep from the same @alfalab/core-components monorepo; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-button | AI (dependencies): Internal sibling dep from the same @alfalab/core-components monorepo; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-navigation-bar-private | AI (dependencies): Internal sibling dep from the same @alfalab/core-components monorepo; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-base-modal | AI (dependencies): Internal sibling dep from the same @alfalab/core-components monorepo; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-typography | AI (dependencies): Internal sibling dep from the same @alfalab/core-components monorepo; stable pattern across all versions. | ai | |
| phantom-deps | phantom-dep:@types/react-transition-group | AI (phantom-deps): Type-only package declared as runtime dep in a TS component library; not directly imported by convention. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 3.1.6 | 11 / 0 | |
| 3.1.5 | 11 / 0 | |
| 3.1.4 | 11 / 0 | |
| 3.1.3 | 11 / 0 | |
| 3.1.2 | 11 / 0 | |
| 3.1.1 | 11 / 0 | |
| 3.1.0 | 11 / 0 | |
| 3.0.7 | 11 / 0 | |
| 3.0.6 | 11 / 0 | |
| 3.0.5 | 11 / 0 | |
| 3.0.4 | 11 / 0 | |
| 3.0.3 | 11 / 0 | |
| 3.0.2 | 11 / 0 | |
| 3.0.1 | 11 / 0 | |
| 3.0.0 | 11 / 0 | |
| 2.0.13 | 14 / 0 | |
| 2.0.12 | 14 / 0 | |
| 2.0.11 | 14 / 0 | |
| 2.0.10 | 14 / 0 | |
| 2.0.7 | 14 / 0 | |
| 2.0.6 | 14 / 0 | |
| 2.0.5 | 14 / 0 |
v3.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.