@alfalab/core-components-base-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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Entire @alfalab/core-components suite published via bot without provenance; stable pattern across all versions. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): react-remove-scroll is a legitimate, widely-used scroll-lock library; appropriate addition for a modal component. | ai | |
| phantom-deps | phantom-dep:@types/react-transition-group | AI (phantom-deps): Types package declared as runtime dep in monorepo pattern; not a real phantom dep concern. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 7.1.4 | 13 / 0 | |
| 7.1.3 | 13 / 0 | |
| 7.1.2 | 13 / 0 | |
| 7.1.1 | 13 / 0 | |
| 7.1.0 | 13 / 0 | |
| 7.0.1 | 13 / 0 | |
| 7.0.0 | 13 / 0 | |
| 6.0.2 | 12 / 0 |
v7.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.