← Home

babel-plugin-ava-throws-helper

npm Repository Homepage

Babel plugin for protecting against improper use of `t.throws()` in AVA

6
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

jamestalmagenovemberbornsindresorhusvdemedes

Keywords

babel-pluginbabelhelperavaassertionthrows

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): jamestalmage → novemberborn is a documented AVA core team maintainer transition; both are well-known contributors to the avajs ecosystem. Not a takeover signal. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy aligns with the maintainer handoff period within the AVA project; no other suspicious signals present. ai

Versions (showing 6 of 6)

Version Deps Published
1.0.0 2 / 3
0.1.0 2 / 3
0.0.5 2 / 3
0.0.4 2 / 3
0.0.3 2 / 3
0.0.2 0 / 3

v1.0.0

2 findings
HIGH Publisher changed: jamestalmage → novemberborn (on 2017-01-17) provenance

This version was published by a different npm account than previous versions on 2017-01-17. This could indicate a legitimate maintainer transition or an account compromise.

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.5

1 finding
LOW No provenance attestation provenance

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

v0.0.4

1 finding
LOW No provenance attestation provenance

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

v0.0.3

1 finding
LOW No provenance attestation provenance

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

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