@alfalab/core-components-select-with-tags
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): Same-org sibling dependency in a well-established monorepo. | ai | |
| phantom-deps | phantom-dep:@alfalab/core-components-shared | AI (phantom-deps): Same-org sibling; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-mq | AI (dependencies): Sibling @alfalab monorepo package; not an independent risk. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-tag | AI (dependencies): Sibling @alfalab monorepo package; not an independent risk. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-input | AI (dependencies): Sibling @alfalab monorepo package; not an independent risk. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-select | AI (dependencies): Sibling @alfalab monorepo package; not an independent risk. | ai | |
| dependencies | unvetted-dep:@alfalab/hooks | AI (dependencies): Sibling @alfalab monorepo package; not an independent risk. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-bottom-sheet | AI (dependencies): Sibling @alfalab monorepo package; not an independent risk. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-form-control | AI (dependencies): Sibling @alfalab monorepo package; not an independent risk. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Consistent with @alfalab monorepo publish pattern; not a spam package. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-popover | AI (dependencies): Sibling @alfalab monorepo package; not an independent risk. | ai | |
| dependencies | unvetted-dep:@alfalab/icons-glyph | AI (dependencies): Sibling @alfalab monorepo package; not an independent risk. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 10.1.10 | 12 / 0 | |
| 10.1.9 | 12 / 0 | |
| 10.1.8 | 12 / 0 | |
| 10.1.7 | 12 / 0 | |
| 10.1.6 | 12 / 0 | |
| 10.1.5 | 12 / 0 | |
| 9.0.9 | 11 / 0 | |
| 9.0.7 | 11 / 0 | |
| 9.0.6 | 11 / 0 | |
| 9.0.5 | 11 / 0 | |
| 9.0.4 | 11 / 0 | |
| 8.8.3 | 12 / 0 | |
| 8.8.2 | 12 / 0 |
v10.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.