@ewizardjs/settings
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Established publisher (ewizardjs-team) with clean track record; no suspicious changes in this version. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established package; missing description is cosmetic, not a malware signal. | ai | |
| provenance | no-provenance | AI (provenance): Only ~12% of npm has provenance; not a disqualifier for mature packages. | ai | |
| dependencies | unvetted-dep:@ewizardjs/structure-api | AI (dependencies): Same org scope; consistent with established ewizardjs ecosystem. | ai | |
| dependencies | unvetted-dep:lodash-template | AI (dependencies): Legitimate utility dep; no malware indicators in this package context. | ai | |
| dependencies | unvetted-dep:@ewizardjs/settings-strategies | AI (dependencies): Same org scope; consistent with established ewizardjs ecosystem. | ai | |
| dependencies | unvetted-dep:@ewizardjs/system-settings | AI (dependencies): Same org scope; consistent with established ewizardjs ecosystem. | ai | |
| dependencies | unvetted-dep:string-to-regexp | AI (dependencies): Small utility dep; no malware indicators in this package context. | ai | |
| dependencies | unvetted-dep:@ewizardjs/structure | AI (dependencies): Same org scope; consistent with established ewizardjs ecosystem. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 4.7.4 | 12 / 15 | |
| 4.7.3 | 12 / 15 | |
| 4.7.2 | 12 / 15 | |
| 4.7.0 | 11 / 14 | |
| 4.6.0 | 11 / 14 | |
| 4.5.1 | 11 / 15 | |
| 4.5.0 | 11 / 15 |
v4.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.