@definitelytyped/header-parser
This library parses package.jsons of [DefinitelyTyped](https://github.com/DefinitelyTyped/DefinitelyTyped) types. Its name is left over from when package information was stored in textual headers.
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): microsoft1es is a Microsoft org account; consistent with internal team management of DefinitelyTyped tooling. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of sheetalkamat alongside microsoft1es addition is an expected Microsoft org account rotation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by resumed publishing is consistent with periodic DefinitelyTyped-tools release cadence, not takeover. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal tooling package; sparse README and no keywords are expected for this org's monorepo packages. | ai | |
| dependencies | unvetted-dep:@definitelytyped/utils | AI (dependencies): Sibling package in the same microsoft/DefinitelyTyped-tools monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@definitelytyped/typescript-versions | AI (dependencies): Sibling package in the same microsoft/DefinitelyTyped-tools monorepo; stable false positive. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.2.27 | 3 / 1 | |
| 0.2.26 | 3 / 1 | |
| 0.2.25 | 3 / 1 | |
| 0.2.24 | 3 / 1 | |
| 0.2.23 | 3 / 1 | |
| 0.2.22 | 3 / 1 | |
| 0.2.21 | 3 / 1 | |
| 0.2.20 | 3 / 1 |
v0.2.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.