types-tsconfig
Type checking for tsconfig.json
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:.auto/build/complier-options.d.ts | AI (source-diff): Generated TypeScript .d.ts file with long Zod schema union type declarations; long lines are a known artifact of ts-to-zod codegen, not obfuscation. | ai | |
| source-diff | obfuscated-file:.auto/build/index.d.ts | AI (source-diff): Generated TypeScript .d.ts file with long Zod schema union type declarations; long lines are a known artifact of ts-to-zod codegen, not obfuscation. | ai | |
| provenance | no-provenance | AI (provenance): Established package with trusted publisher history; lack of Sigstore provenance is a best-practice gap, not a security risk for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 2.1.1 | 2 / 1 | |
| 2.1.0 | 2 / 1 | |
| 2.0.2 | 2 / 1 | |
| 2.0.0 | 2 / 2 | |
| 1.2.1 | 1 / 1 | |
| 1.2.0 | 1 / 1 | |
| 1.1.2 | 1 / 1 | |
| 1.1.1 | 1 / 1 | |
| 1.1.0 | 0 / 1 | |
| 1.0.0 | 0 / 1 |
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: bconnorwhite.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: bconnorwhite.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: bconnorwhite.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: bconnorwhite.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.