@alfalab/core-components-number-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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@alfalab/core-components-mq | AI (dependencies): Sibling package from the same @alfalab/core-components monorepo; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-input | AI (dependencies): Sibling package from the same @alfalab/core-components monorepo; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-shared | AI (dependencies): Sibling package from the same @alfalab/core-components monorepo; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-icon-button | AI (dependencies): Sibling package from the same @alfalab/core-components monorepo; stable false positive for this package family. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo component package; missing description/repo/keywords is a consistent pattern across the @alfalab suite, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent with other @alfalab monorepo component packages; not a malice indicator. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 4.0.9 | 10 / 0 | |
| 4.0.8 | 10 / 0 | |
| 4.0.7 | 10 / 0 | |
| 4.0.6 | 10 / 0 | |
| 4.0.5 | 10 / 0 | |
| 4.0.4 | 10 / 0 | |
| 4.0.3 | 10 / 0 | |
| 4.0.2 | 10 / 0 | |
| 4.0.1 | 10 / 0 | |
| 4.0.0 | 10 / 0 | |
| 3.0.7 | 10 / 0 | |
| 3.0.6 | 10 / 0 | |
| 3.0.5 | 10 / 0 | |
| 3.0.4 | 10 / 0 | |
| 3.0.3 | 10 / 0 | |
| 2.7.4 | 10 / 0 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.