@types/loglevel — Greenflagged

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

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/pro/	AI (email-domain): The 'email' field is actually a GitHub profile URL in the author string, not an email address. No real domain hijack risk; this is a standard DefinitelyTyped contributor attribution pattern.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Long-established DefinitelyTyped @types package published by the trusted 'types' publisher; lack of Sigstore provenance is expected and acceptable here.	ai	2026/04/24

Versions (showing 9 of 9)

Version	Deps	Published
1.6.3	1 / 0	2019-06-24
1.5.4	0 / 0	2019-02-06
1.5.3	0 / 0	2017-10-18
1.5.2	0 / 0	2017-10-17
1.5.1	0 / 0	2017-09-28
1.5.0	0 / 0	2017-09-26
1.4.30	0 / 0	2017-08-21
1.4.29	0 / 0	2016-09-19
1.4.28	0 / 0	2016-07-14

v1.6.3

1 finding

LOW No provenance attestation provenance

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

v1.5.4

1 finding

LOW No provenance attestation provenance

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

v1.5.3

1 finding

LOW No provenance attestation provenance

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

v1.5.2

1 finding

INFO No provenance attestation provenance

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

v1.5.1

1 finding

LOW No provenance attestation provenance

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

v1.5.0

1 finding

LOW No provenance attestation provenance

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

v1.4.30

1 finding

LOW No provenance attestation provenance

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

v1.4.29

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

2 findings

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

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