← Home

inferno-hydrate

npm Repository Homepage
8
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

havunen

Keywords

babelreactinfernoframeworkinterfacesuser interfacesvdom

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:inferno AI (dependencies): inferno is the core sibling package in the same monorepo; always a legitimate dependency for inferno-hydrate. ai
email-domain unclaimed-email:havunen AI (email-domain): The 'Havunen' value is the author's GitHub username, not an email domain; real email is [email protected]. Stable false positive for this package. ai

Versions (showing 8 of 8)

Version Deps Published
9.1.0 1 / 4
9.0.11 1 / 4
9.0.10 1 / 4
9.0.9 1 / 4
9.0.8 1 / 4
9.0.7 1 / 4
9.0.5 1 / 4
9.0.4 1 / 4

v9.1.0

2 findings
HIGH Unclaimed maintainer email domain: havunen email-domain

Maintainer email 'Havunen' uses domain 'havunen' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.0.11

1 finding
LOW No provenance attestation provenance

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

v9.0.10

1 finding
LOW No provenance attestation provenance

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

v9.0.9

1 finding
LOW No provenance attestation provenance

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

v9.0.8

1 finding
LOW No provenance attestation provenance

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

v9.0.7

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

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