@kaliber/config
Zero dependency, minimal configuration library operating on CONFIG_ENV
1
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
daveykropfeecolorjerryduijmkaliber-ownernhoenderoplarsbijkaliberjanbrualbertkalibermvanbrakelit-traveleryoreljenkinsmdevalk1983guido.evertzensvroom-kalibertomharmsrinus.vhjvandenakkerpgoddijnjvankralingen
Keywords
configuration
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Config loader intentionally requires user-specified config files by path; this is the package's core design. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 0 / 2 |
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.