@ewizardjs/alias-resolver
2
Versions
—
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
serhii_butvasylshylovewizardjs-teamb.hryhorievm.polevchukv.kobyletskiyalexbelov
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer is within the same ewizardjs org; consistent with internal team rotation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal paired with same-org replacement; no cross-org takeover signal. | ai |
v1.2.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
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.