@phyxiusjs/config
Type-safe configuration management with hot reloading, multiple sources, and observability
2
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
rodrigopsasaki
Keywords
configconfigurationenvironmentsettingsphyxiustypescripthot-reloadvalidation
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@phyxiusjs/fp | AI (dependencies): Same-org sibling package from a publisher with 20 approved packages; part of the phyxius monorepo. | ai | |
| provenance | no-provenance | AI (provenance): New package from a monorepo; provenance absence is common and no other risk signals present. | ai |
v0.1.1
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.