@types/babel-generator MIT 11 versions

@types/babel-generator

npm Repository Homepage

TypeScript definitions for babel-generator

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/yortus	AI (email-domain): The 'email' field is actually a GitHub profile URL, not an email address. No real email domain is at risk of hijacking. This is a common pattern in older DefinitelyTyped author fields.	ai	2026/04/24
phantom-deps	phantom-dep:@types/babel-types	AI (phantom-deps): @types/babel-types is a legitimate type dependency for this DefinitelyTyped package, loaded by TypeScript convention rather than direct import.	ai	2026/04/24

Versions (showing 11 of 11)

Version	Deps	Published
6.25.8	1 / 0	2023-11-06
6.25.7	1 / 0	2023-10-17
6.25.6	1 / 0	2023-09-15
6.25.5	1 / 0	2021-12-23
6.25.4	1 / 0	2021-07-06
6.25.3	1 / 0	2019-02-13
6.25.2	1 / 0	2018-06-12
6.25.1	1 / 0	2017-11-08
6.25.0	1 / 0	2017-07-07
6.7.14	1 / 0	2016-09-19
6.7.13	1 / 0	2016-07-14

v6.25.8

1 finding

LOW No provenance attestation provenance

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

v6.25.7

1 finding

LOW No provenance attestation provenance

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

v6.25.6

1 finding

LOW No provenance attestation provenance

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

v6.25.5

1 finding

LOW No provenance attestation provenance

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

v6.25.4

1 finding

LOW No provenance attestation provenance

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

v6.25.3

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