@types/invariant MIT 11 versions

@types/invariant

npm Repository Homepage

TypeScript definitions for invariant

11

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

types

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
email-domain	unclaimed-email:https://github.com/bennett000/	AI (email-domain): The 'email' field is a GitHub profile URL, not an email address. No actual email domain exists to hijack. This is a DefinitelyTyped author attribution pattern, not a real email domain risk.	ai	2026/04/24
bogus-package	bogus-package	AI (bogus-package): @types/* packages are intentionally tiny type-only packages with no runtime deps or keywords. These signals are expected and stable for all DefinitelyTyped packages.	ai	2026/04/24

Versions (showing 11 of 11)

Version	Deps	Published
2.2.37	0 / 0	2023-11-07
2.2.36	0 / 0	2023-10-18
2.2.35	0 / 0	2021-08-26
2.2.34	0 / 0	2020-09-01
2.2.33	0 / 0	2020-05-15
2.2.32	0 / 0	2020-04-23
2.2.31	0 / 0	2019-12-20
2.2.30	0 / 0	2019-07-01
2.2.29	0 / 0	2017-08-21
2.2.28	0 / 0	2016-09-19
2.2.27	0 / 0	2016-07-14

v2.2.37

1 finding

LOW No provenance attestation provenance

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

v2.2.36

1 finding

LOW No provenance attestation provenance

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

v2.2.35

1 finding

LOW No provenance attestation provenance

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

v2.2.34

1 finding

LOW No provenance attestation provenance

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

v2.2.33

1 finding

LOW No provenance attestation provenance

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

v2.2.32

1 finding

LOW No provenance attestation provenance

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

v2.2.31

1 finding

LOW No provenance attestation provenance

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

v2.2.30

1 finding

LOW No provenance attestation provenance

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

v2.2.29

1 finding

LOW No provenance attestation provenance

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

v2.2.28

1 finding

LOW No provenance attestation provenance

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

v2.2.27

2 findings

HIGH Unclaimed maintainer email domain: https://github.com/bennett000/ email-domain

Maintainer email 'https://github.com/bennett000/' uses domain 'https://github.com/bennett000/' 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.