mesh-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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@fastify/pre-commit | AI (phantom-deps): @fastify/pre-commit is a git hook tool used via package.json pre-commit config, not imported at runtime. | ai | |
| semgrep | semgrep:env-bulk-read | AI (semgrep): Core feature of a config library; reading all process.env entries is intentional and documented behavior. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.3.4 | 0 / 8 | |
| 1.3.3 | 0 / 8 | |
| 1.3.2 | 0 / 8 | |
| 1.3.1 | 0 / 8 | |
| 1.3.0 | 0 / 9 | |
| 1.2.4 | 0 / 9 | |
| 1.2.3 | 2 / 9 | |
| 1.2.2 | 3 / 8 |
v1.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.