@autosoft/tsconfig
A base for TypeScript projects.
2
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
bconnorwhite
Keywords
typescripttsconfigtsconfig.jsonbaseautoautosoftautoreposwc
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:ts-node | AI (phantom-deps): tsconfig base packages reference ts-node in config settings, not as a JS import. This is expected and stable for this package. | ai | |
| phantom-deps | phantom-dep:@swc/core | AI (phantom-deps): tsconfig base packages reference @swc/core in config settings, not as a JS import. Expected pattern for this package type. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): typescript is a toolchain dependency referenced by tsconfig convention, not a JS import. Expected for this package type. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node is a type definitions package loaded by convention in TypeScript projects. Not a JS import; expected for a tsconfig base package. | ai |
v1.0.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
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.