← Home

@types/babylon

npm Repository Homepage

TypeScript definitions for babylon

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

SourceRuleReasonAccepted byWhen
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. This is a stable false positive for this package. ai
phantom-deps phantom-dep:@types/babel-types AI (phantom-deps): @types/babel-types is a type-level dependency loaded by convention in TypeScript definition packages, not a runtime import. Stable false positive for @types packages. ai
provenance no-provenance AI (provenance): Package is ~10 years old, predating Sigstore provenance on npm. No provenance is expected for this package. ai

Versions (showing 13 of 13)

Version Deps Published
6.16.9 1 / 0
6.16.8 1 / 0
6.16.7 1 / 0
6.16.6 1 / 0
6.16.5 1 / 0
6.16.4 1 / 0
6.16.3 1 / 0
6.16.2 1 / 0
6.16.1 1 / 0
6.16.0 1 / 0
6.7.15 1 / 0
6.7.14 1 / 0
6.7.13 1 / 0

v6.16.9

1 finding
LOW No provenance attestation provenance

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

v6.16.8

1 finding
LOW No provenance attestation provenance

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

v6.16.7

1 finding
LOW No provenance attestation provenance

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

v6.16.6

1 finding
LOW No provenance attestation provenance

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

v6.16.5

1 finding
LOW No provenance attestation provenance

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

v6.16.4

1 finding
LOW No provenance attestation provenance

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

v6.16.3

1 finding
LOW No provenance attestation provenance

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

v6.16.2

1 finding
LOW No provenance attestation provenance

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

v6.16.1

1 finding
LOW No provenance attestation provenance

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

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