← Home

@alfalab/core-components-amount-input

19
Versions
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.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): All new deps are well-known packages (lodash, maskito, react-merge-refs); consistent with component library growth. ai
npm-metadata no-description AI (npm-metadata): Stable pattern for this monorepo component; not indicative of malicious intent. ai
dependencies unvetted-dep:@alfalab/core-components-input AI (dependencies): Sibling @alfalab monorepo package; same publisher ecosystem, stable false positive. ai
dependencies unvetted-dep:@alfalab/core-components-shared AI (dependencies): Sibling @alfalab monorepo package; same publisher ecosystem, stable false positive. ai
dependencies unvetted-dep:@alfalab/hooks AI (dependencies): Sibling @alfalab monorepo package; same publisher ecosystem, stable false positive. ai
dependencies unvetted-dep:@alfalab/core-components-number-input AI (dependencies): Sibling @alfalab monorepo package; same publisher ecosystem, stable false positive. ai
bogus-package bogus-package AI (bogus-package): Monorepo dist package; missing metadata is a known pattern for this ecosystem, not a spam indicator. ai
dependencies unvetted-dep:@alfalab/core-components-with-suffix AI (dependencies): Sibling @alfalab monorepo package; same publisher ecosystem, stable false positive. ai
dependencies unvetted-dep:@alfalab/utils AI (dependencies): Sibling @alfalab monorepo package; same publisher ecosystem, stable false positive. ai

Versions (showing 19 of 19)

Version Deps Published
9.2.6 13 / 0
9.2.5 13 / 0
9.2.4 13 / 0
9.2.3 13 / 0
9.2.2 13 / 0
9.2.1 13 / 0
9.2.0 13 / 0
9.1.3 13 / 0
9.1.2 13 / 0
9.1.1 13 / 0
9.1.0 13 / 0
9.0.1 13 / 0
9.0.0 13 / 0
8.2.0 8 / 0
8.1.6 8 / 0
8.1.5 8 / 0
8.1.4 8 / 0
8.1.3 8 / 0
7.16.0 8 / 0

v9.2.6

1 finding
LOW No provenance attestation provenance

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

v9.2.5

1 finding
LOW No provenance attestation provenance

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

v9.2.4

1 finding
LOW No provenance attestation provenance

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

v9.2.3

1 finding
LOW No provenance attestation provenance

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

v9.2.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.

v9.2.1

1 finding
LOW No provenance attestation provenance

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

v9.2.0

1 finding
LOW No provenance attestation provenance

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

v9.1.3

1 finding
LOW No provenance attestation provenance

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

v9.1.2

1 finding
LOW No provenance attestation provenance

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

v9.1.1

1 finding
LOW No provenance attestation provenance

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

v9.1.0

1 finding
LOW No provenance attestation provenance

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

v9.0.1

1 finding
LOW No provenance attestation provenance

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

v9.0.0

1 finding
LOW No provenance attestation provenance

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

v8.2.0

1 finding
LOW No provenance attestation provenance

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

v8.1.6

1 finding
LOW No provenance attestation provenance

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

v8.1.5

1 finding
LOW No provenance attestation provenance

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

v8.1.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.

v8.1.3

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.

v7.16.0

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.