@mitm/config
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): This is a configuration utility package whose core purpose is exposing environment variables. Spreading process.env is expected, intentional behavior — not a security risk in this context. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped internal package (@mitm/) from a trusted publisher with 4+ year history. Sparse metadata is expected for internal/organizational packages, not a spam/malware indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal scoped package from established publisher; missing description is a style issue, not a security signal. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 2.3.0 | 1 / 0 | |
| 2.2.0 | 1 / 0 | |
| 2.1.0 | 1 / 0 | |
| 2.0.0 | 1 / 0 | |
| 1.2.0 | 0 / 0 | |
| 1.1.1 | 0 / 0 | |
| 1.1.0 | 0 / 0 | |
| 1.0.0 | 0 / 0 |
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
2 findingsSpreading entire process.env into an object — may capture all secrets 24 | var _a; 25 | // eslint-disable-next-line @typescript-eslint/no-explicit-any > 26 | return { ...process.env, ...(_a = globalThis.DYNAMIC_ENVIRONMENT_VARIABLES) !== null && _a !== void 0 ? _a : {} }; 27 | } 28 | //# sourceMappingURL=getters.js.map
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.