@alfalab/core-components-international-phone-input
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 |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): Active component library with frequent releases; large file additions reflect legitimate refactoring/bundling changes. | ai | |
| provenance | no-provenance | AI (provenance): Established @alfalab org package; lack of provenance is consistent across the package family. | ai | |
| dependencies | unvetted-dep:@alfalab/icons-glyph | AI (dependencies): Sibling package in the @alfalab ecosystem; stable false positive for this monorepo. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-mq | AI (dependencies): Sibling package in the @alfalab ecosystem; stable false positive for this monorepo. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-input | AI (dependencies): Sibling package in the @alfalab ecosystem; stable false positive for this monorepo. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-types | AI (dependencies): Sibling package in the @alfalab ecosystem; stable false positive for this monorepo. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-select | AI (dependencies): Sibling package in the @alfalab ecosystem; stable false positive for this monorepo. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-shared | AI (dependencies): Sibling package in the @alfalab ecosystem; stable false positive for this monorepo. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-input-autocomplete | AI (dependencies): Sibling package in the @alfalab ecosystem; stable false positive for this monorepo. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; missing metadata is a structural pattern, not a spam indicator. | ai | |
| dependencies | unvetted-dep:@alfalab/hooks | AI (dependencies): Sibling package in the @alfalab ecosystem; stable false positive for this monorepo. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 4.0.16 | 13 / 0 | |
| 4.0.15 | 13 / 0 | |
| 4.0.14 | 13 / 0 | |
| 4.0.13 | 13 / 0 | |
| 4.0.12 | 13 / 0 | |
| 4.0.11 | 13 / 0 | |
| 4.0.10 | 13 / 0 | |
| 4.0.9 | 13 / 0 | |
| 4.0.8 | 13 / 0 | |
| 4.0.7 | 13 / 0 | |
| 4.0.6 | 13 / 0 | |
| 4.0.5 | 13 / 0 | |
| 4.0.4 | 13 / 0 | |
| 4.0.3 | 13 / 0 | |
| 4.0.2 | 13 / 0 | |
| 4.0.1 | 13 / 0 | |
| 4.0.0 | 13 / 0 | |
| 3.2.13 | 13 / 0 | |
| 3.2.12 | 13 / 0 | |
| 3.2.11 | 13 / 0 | |
| 3.2.10 | 13 / 0 | |
| 3.2.9 | 13 / 0 | |
| 3.2.8 | 13 / 0 | |
| 3.2.7 | 13 / 0 | |
| 3.2.6 | 13 / 0 | |
| 3.2.5 | 13 / 0 | |
| 3.2.4 | 13 / 0 | |
| 3.2.3 | 13 / 0 | |
| 3.2.2 | 13 / 0 | |
| 3.2.1 | 13 / 0 | |
| 2.8.5 | 12 / 0 | |
| 2.8.4 | 12 / 0 | |
| 2.8.2 | 12 / 0 |
v4.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.6
2 findingsThis version was published by a different npm account than previous versions on 2025-12-30. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.5
2 findingsThis version was published by a different npm account than previous versions on 2025-12-22. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.