@adobe/aio-lib-console
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 |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in bin/validate_spec.js loads a user-supplied spec file path — intentional CLI behavior, not arbitrary module loading. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 5.8.0 | 5 / 28 | |
| 5.7.0 | 5 / 28 | |
| 5.6.0 | 7 / 28 | |
| 5.5.0 | 7 / 28 |
v5.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.