@spinajs/configuration
framework configuration module
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): Configuration framework intentionally merges process.env into config object; stable design pattern across all versions. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 456 versions; lack of provenance is consistent across all releases and not a new risk. | ai |
Versions (showing 5 of 111)
| Version | Deps | Published |
|---|---|---|
| 2.0.367 | 11 / 1 | |
| 2.0.363 | 11 / 1 | |
| 2.0.362 | 11 / 1 | |
| 2.0.361 | 11 / 1 | |
| 2.0.360 | 11 / 1 |
v2.0.367
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.363
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.362
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.361
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.360
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.