@types/dockerode
TypeScript definitions for dockerode
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/* packages are loaded by convention, not direct import; stable false positive for all DefinitelyTyped stubs. | ai | |
| phantom-deps | phantom-dep:@types/ssh2 | AI (phantom-deps): Type-only dependency loaded by convention; not directly imported in .d.ts files. | ai | |
| phantom-deps | phantom-dep:@types/docker-modem | AI (phantom-deps): Type-only dependency loaded by convention; not directly imported in .d.ts files. | ai |
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.