@adobe/aem-cli
AEM CLI
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@adobe/helix-html2md | AI (dependencies): First-party Adobe/helix package from same monorepo org. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are trusted first-party @adobe/helix-* packages. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): CLI tool; deps referenced in config files rather than direct imports is normal for this package. | ai | |
| phantom-deps | phantom-dep:shelljs | AI (phantom-deps): CLI tool; deps referenced in config files rather than direct imports is normal for this package. | ai | |
| semgrep | semgrep:env-bulk-read | AI (semgrep): CLI config loader filtering process.env for HLX_ prefixed vars; expected pattern for this package. | ai | |
| phantom-deps | phantom-dep:proxy-agent | AI (phantom-deps): CLI tool; deps referenced in config files rather than direct imports is normal for this package. | ai | |
| phantom-deps | phantom-dep:progress | AI (phantom-deps): CLI tool; deps referenced in config files rather than direct imports is normal for this package. | ai | |
| phantom-deps | phantom-dep:glob | AI (phantom-deps): CLI tool; deps referenced in config files rather than direct imports is normal for this package. | ai |
Versions (showing 27 of 229)
| Version | Deps | Published |
|---|---|---|
| 16.5.9 | 35 / 17 | |
| 16.5.8 | 35 / 17 | |
| 16.5.7 | 35 / 17 | |
| 16.5.6 | 35 / 17 | |
| 16.5.5 | 35 / 17 | |
| 16.5.4 | 35 / 17 | |
| 16.5.3 | 35 / 17 | |
| 16.5.2 | 35 / 17 | |
| 16.5.1 | 35 / 17 | |
| 16.5.0 | 35 / 17 | |
| 16.4.0 | 35 / 17 | |
| 16.3.26 | 35 / 17 | |
| 16.3.25 | 35 / 17 | |
| 16.3.24 | 35 / 17 | |
| 16.3.23 | 35 / 17 | |
| 16.3.22 | 35 / 17 | |
| 16.3.21 | 35 / 17 | |
| 16.3.20 | 35 / 17 | |
| 16.3.19 | 35 / 17 | |
| 16.3.18 | 35 / 17 | |
| 16.3.17 | 35 / 17 | |
| 16.3.16 | 35 / 17 | |
| 16.3.15 | 35 / 17 | |
| 16.3.14 | 35 / 17 | |
| 16.3.13 | 35 / 17 | |
| 16.3.12 | 35 / 17 | |
| 16.3.11 | 35 / 17 |
v16.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.3.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.3.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.3.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.3.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.3.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.3.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.3.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.3.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.3.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.3.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.3.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.3.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.3.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.3.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.