@alfalab/core-components-input-autocomplete MIT 31 versions

@alfalab/core-components-input-autocomplete

npm

31

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

siebensiebenheymdalligor-alfa-testpraiz90dmitryshkindercore-ds-botqrik116sashabullsklartell4mea.shatokhinthediamonddogefulcanelleehextionbradobreyu

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@alfalab/hooks	AI (dependencies): Sibling @alfalab monorepo package; same publisher/ecosystem, not an independent risk.	ai	2026/05/16
dependencies	unvetted-dep:@alfalab/core-components-mq	AI (dependencies): Sibling @alfalab monorepo package; same publisher/ecosystem, not an independent risk.	ai	2026/05/16
dependencies	unvetted-dep:@alfalab/core-components-input	AI (dependencies): Sibling @alfalab monorepo package; same publisher/ecosystem, not an independent risk.	ai	2026/05/16
dependencies	unvetted-dep:@alfalab/core-components-select	AI (dependencies): Sibling @alfalab monorepo package; same publisher/ecosystem, not an independent risk.	ai	2026/05/16
dependencies	unvetted-dep:@alfalab/core-components-shared	AI (dependencies): Sibling @alfalab monorepo package; same publisher/ecosystem, not an independent risk.	ai	2026/05/16
dependencies	unvetted-dep:@alfalab/core-components-popover	AI (dependencies): Sibling @alfalab monorepo package; same publisher/ecosystem, not an independent risk.	ai	2026/05/16
dependencies	unvetted-dep:@alfalab/core-components-form-control	AI (dependencies): Sibling @alfalab monorepo package; same publisher/ecosystem, not an independent risk.	ai	2026/05/16
dependencies	unvetted-dep:@alfalab/core-components-status-badge	AI (dependencies): Sibling @alfalab monorepo package; same publisher/ecosystem, not an independent risk.	ai	2026/05/16
bogus-package	bogus-package	AI (bogus-package): Scoped monorepo component package; missing metadata is typical for dist-published packages, not a spam indicator.	ai	2026/05/16

Versions (showing 31 of 31)

Version	Deps	Published
14.0.16	13 / 0	2026-06-05
14.0.15	13 / 0	2026-05-29
14.0.14	13 / 0	2026-05-25
14.0.13	13 / 0	2026-05-22
14.0.12	13 / 0	2026-05-08
14.0.11	13 / 0	2026-04-17
14.0.10	13 / 0	2026-04-10
14.0.9	13 / 0	2026-03-20
14.0.8	13 / 0	2026-03-06
14.0.7	13 / 0	2026-02-27
14.0.6	13 / 0	2026-02-24
14.0.5	13 / 0	2026-02-20
14.0.4	13 / 0	2026-02-13
14.0.3	13 / 0	2026-02-13
14.0.2	13 / 0	2026-02-09
14.0.1	13 / 0	2026-02-05
14.0.0	13 / 0	2026-02-04
13.1.5	13 / 0	2026-04-09
13.1.4	13 / 0	2026-02-27
13.1.3	13 / 0	2026-02-13
13.1.2	13 / 0	2026-02-10
13.1.1	13 / 0	2026-01-30
13.1.0	13 / 0	2026-01-23
13.0.10	13 / 0	2026-01-19
13.0.7	13 / 0	2025-12-08
13.0.6	13 / 0	2025-11-13
13.0.5	13 / 0	2025-11-07
13.0.4	13 / 0	2025-11-05
12.10.5	13 / 1	2026-04-08
12.10.4	13 / 1	2026-02-10
12.10.2	13 / 1	2025-12-05

v14.0.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.0.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.0.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.0.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.0.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.0.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v14.0.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.0.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.0.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.0.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.0.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.0.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.0.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v14.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v13.1.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v13.1.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v13.1.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v13.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v13.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v13.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v13.0.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v13.0.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v13.0.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v13.0.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v13.0.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v12.10.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v12.10.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v12.10.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.