inferno-create-element
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:inferno | AI (dependencies): inferno is the core package of the same monorepo; always a legitimate peer dependency for inferno-create-element. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 9.1.0 | 1 / 2 | |
| 9.0.11 | 1 / 2 | |
| 9.0.10 | 1 / 2 | |
| 9.0.9 | 1 / 2 | |
| 9.0.8 | 1 / 2 | |
| 9.0.7 | 1 / 2 | |
| 9.0.5 | 1 / 2 | |
| 9.0.4 | 1 / 2 |
v9.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.8
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.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.