← Home

iferr

npm Repository Homepage

Higher-order functions for easier error handling

8
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

nadav

Keywords

errorerrors

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff net-exec-file:node_modules.old/coffeescript/lib/coffeescript/browser.js AI (source-diff): This is CoffeeScript's legitimate browser.js accidentally bundled in node_modules.old/; not malicious code authored by the iferr maintainer. ai
source-diff net-exec-file:node_modules.old/coffeescript/lib/coffeescript/command.js AI (source-diff): This is CoffeeScript's legitimate command.js accidentally bundled in node_modules.old/; not malicious code authored by the iferr maintainer. ai

Versions (showing 8 of 8)

Version Deps Published
1.0.2 0 / 2
1.0.0 0 / 2
0.1.5 0 / 2
0.1.4 0 / 2
0.1.3 0 / 2
0.1.2 0 / 2
0.1.1 0 / 2
0.1.0 0 / 2

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.0

1 finding
LOW No provenance attestation provenance

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

v0.1.5

1 finding
LOW No provenance attestation provenance

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

v0.1.4

1 finding
LOW No provenance attestation provenance

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

v0.1.3

1 finding
LOW No provenance attestation provenance

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

v0.1.2

1 finding
LOW No provenance attestation provenance

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

v0.1.1

1 finding
LOW No provenance attestation provenance

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

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