@alfalab/core-components-file-upload-item
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Monorepo component package; missing description/keywords/repo URL is a consistent pattern across all @alfalab packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Same monorepo pattern; stable false positive for this package family. | ai | |
| provenance | no-provenance | AI (provenance): Publisher has 643 approved packages without provenance; consistent org-wide pattern. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 8.0.10 | 8 / 0 | |
| 8.0.9 | 8 / 0 | |
| 8.0.8 | 8 / 0 | |
| 8.0.7 | 8 / 0 | |
| 8.0.6 | 8 / 0 | |
| 8.0.5 | 8 / 0 | |
| 8.0.4 | 8 / 0 | |
| 8.0.3 | 8 / 0 | |
| 8.0.2 | 8 / 0 | |
| 8.0.1 | 8 / 0 | |
| 8.0.0 | 8 / 0 | |
| 7.3.1 | 8 / 0 | |
| 7.3.0 | 8 / 0 | |
| 7.2.1 | 8 / 0 |
v8.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.