@dotcom-tool-kit/telemetry
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 |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): Intentional env pass-through to child process in FT's telemetry tool; not exfiltration. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 1 / 1 |
v1.0.0
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/financial-times/dotcom-tool-kit/blob/ae77eaf8bcb6bd3df3068770997c7f8cbe50a972/lib/index.js#L67 65 | // gets picked up if we explicitly pass the environment here instead of 66 | // implicitly? > 67 | env: { ...process.env } 68 | }); 69 | // print all errors (or anything else that's logged to stderr) as winston
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.