@types/expect MIT 11 versions

@types/expect

npm

Stub TypeScript definitions entry for expect, which provides its own types definitions

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/jmreidy/	AI (email-domain): The 'email' field is a GitHub profile URL used as author contact, not an actual email domain. No registerable domain is at risk; this is a stable false positive for this package.	ai	2026/04/22
bogus-package	bogus-package	AI (bogus-package): Stub types packages legitimately have minimal README, no repo, no keywords, and tiny payloads. This is the correct form for a deprecated type definition shim.	ai	2026/04/21
dependencies	unvetted-dep:expect	AI (dependencies): expect is the actual package this stub types package wraps; unvetted status is expected and acceptable for the core dependency.	ai	2026/04/21
phantom-deps	phantom-dep:expect	AI (phantom-deps): Phantom dependency on expect is expected; stub types packages declare but do not directly import their wrapped package.	ai	2026/04/21

Versions (showing 11 of 11)

Version	Deps	Published
24.3.2	1 / 0	2024-10-23
24.3.1	1 / 0	2024-10-23
24.3.0	1 / 0	2019-11-06
1.20.4	0 / 0	2019-02-13
1.20.3	0 / 0	2018-02-26
1.20.2	0 / 0	2017-08-21
1.20.1	0 / 0	2017-03-24
1.20.0	0 / 0	2017-01-06
1.13.31	0 / 0	2016-11-29
1.13.30	0 / 0	2016-09-19
1.13.29	0 / 0	2016-07-14

v1.20.4

1 finding

LOW No provenance attestation provenance

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

v1.20.3

1 finding

LOW No provenance attestation provenance

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

v1.20.2

1 finding

LOW No provenance attestation provenance

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

v1.20.1

1 finding

LOW No provenance attestation provenance

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

v1.20.0

1 finding

LOW No provenance attestation provenance

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

v1.13.31

1 finding

LOW No provenance attestation provenance

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

v1.13.30

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.

v1.13.29

2 findings

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

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