@types/parse-glob
TypeScript definitions for parse-glob
Supply chain provenance
Status for the latest visible version.
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
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/glen-84 | AI (email-domain): The 'email' field is a GitHub profile URL, not an email address. The analyzer is misinterpreting a URL as an email domain — no real domain hijack risk exists. | ai | |
| provenance | no-provenance | AI (provenance): DefinitelyTyped @types/* packages published by the trusted 'types' publisher do not include Sigstore provenance; this is expected and not a risk. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 3.0.32 | 0 / 0 | |
| 3.0.31 | 0 / 0 | |
| 3.0.30 | 0 / 0 | |
| 3.0.29 | 0 / 0 | |
| 3.0.28 | 0 / 0 |
v3.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.28
2 findingsMaintainer email 'https://github.com/glen-84' uses domain 'https://github.com/glen-84' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.