@types/babel-types MIT 24 versions

@types/babel-types

npm Repository Homepage

TypeScript definitions for babel-types

24

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/yortus	AI (email-domain): The 'email' field is a GitHub profile URL, not an actual email address. The analyzer is misinterpreting a URL as an email domain. No real domain hijack risk exists.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Long-established DefinitelyTyped package published by the trusted 'types' publisher; lack of provenance attestation is expected and not a risk signal here.	ai	2026/04/24

Versions (showing 24 of 24)

Version	Deps	Published
7.0.16	0 / 0	2024-10-23
7.0.15	0 / 0	2023-11-20
7.0.14	0 / 0	2023-11-06
7.0.13	0 / 0	2023-10-17
7.0.12	0 / 0	2023-09-15
7.0.11	0 / 0	2021-08-26
7.0.10	0 / 0	2021-07-06
7.0.9	0 / 0	2020-09-02
7.0.8	0 / 0	2020-07-06
7.0.7	0 / 0	2019-04-24
7.0.6	0 / 0	2019-02-27
7.0.5	0 / 0	2019-02-13
7.0.4	0 / 0	2018-06-18
7.0.3	0 / 0	2018-06-12
7.0.2	0 / 0	2018-05-08
7.0.1	0 / 0	2018-02-26
7.0.0	0 / 0	2017-12-18
6.25.2	0 / 0	2017-11-28
6.25.1	0 / 0	2017-07-20
6.25.0	0 / 0	2017-07-18
6.7.16	0 / 0	2017-05-05
6.7.15	0 / 0	2017-05-05
6.7.14	0 / 0	2016-09-19
6.7.13	0 / 0	2016-07-14

v7.0.16

1 finding

LOW No provenance attestation provenance

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

v7.0.15

1 finding

LOW No provenance attestation provenance

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

v7.0.14

1 finding

LOW No provenance attestation provenance

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

v7.0.13

1 finding

LOW No provenance attestation provenance

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

v7.0.12

1 finding

LOW No provenance attestation provenance

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

v7.0.11

1 finding

LOW No provenance attestation provenance

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

v7.0.10

1 finding

LOW No provenance attestation provenance

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

v7.0.9

1 finding

LOW No provenance attestation provenance

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

v7.0.8

1 finding

LOW No provenance attestation provenance

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

v7.0.7

1 finding

LOW No provenance attestation provenance

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

v7.0.6

1 finding

LOW No provenance attestation provenance

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

v7.0.5

1 finding

LOW No provenance attestation provenance

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

v7.0.4

1 finding

LOW No provenance attestation provenance

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

v7.0.3

1 finding

LOW No provenance attestation provenance

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

v7.0.2

1 finding

LOW No provenance attestation provenance

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

v7.0.1

1 finding

LOW No provenance attestation provenance

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

v7.0.0

1 finding

LOW No provenance attestation provenance

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

v6.25.2

1 finding

LOW No provenance attestation provenance

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

v6.25.1

1 finding

LOW No provenance attestation provenance

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

v6.25.0

1 finding

LOW No provenance attestation provenance

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

v6.7.16

1 finding

LOW No provenance attestation provenance

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

v6.7.15

1 finding

LOW No provenance attestation provenance

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

v6.7.14

1 finding

LOW No provenance attestation provenance

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

v6.7.13

2 findings

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

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