← Home

@adobe/aio-lib-console

npm Repository Homepage
10
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

marbectripodgarthdblazdadobe-adminpatrickfultontrieloffshazronkrisnyedcpfsdknatebaldwindevongovettaspro83symanovidpfisterstefan-guggisbergrofekptdobeadobehallsfullcolorcoderdjaeggidylandepassmhaackamol-anandstopp-adobedotenduh_schmidtasthabh23zdahbituicufmeschbe

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Normal Adobe org team rotation; publisher track record is strong. ai
maintainer-change maintainer-removed AI (maintainer-change): Consistent with team rotation, not takeover. ai
bogus-package bogus-package AI (bogus-package): Established, widely-used Adobe SDK; README heuristic false positive. ai
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 10 of 10)

Version Deps Published
5.8.0 5 / 28
5.7.0 5 / 28
5.6.0 7 / 28
5.5.0 7 / 28
5.4.2 7 / 28
5.4.1 7 / 28
5.4.0 7 / 28
5.3.2 6 / 28
5.3.1 6 / 28
5.3.0 5 / 28

v5.4.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.4.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.3.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.3.0

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.