@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 100 of 228)
| Version | Deps | Published |
|---|---|---|
| 16.10.39 | 36 / 16 | |
| 16.10.38 | 36 / 17 | |
| 16.10.37 | 36 / 17 | |
| 16.10.36 | 36 / 17 | |
| 16.10.35 | 36 / 17 | |
| 16.10.34 | 36 / 17 | |
| 16.10.33 | 36 / 17 | |
| 16.10.32 | 36 / 17 | |
| 16.10.31 | 36 / 16 | |
| 16.10.30 | 36 / 16 | |
| 16.10.29 | 36 / 16 | |
| 16.10.28 | 36 / 16 | |
| 16.10.27 | 36 / 16 | |
| 16.10.26 | 36 / 16 | |
| 16.10.25 | 36 / 16 | |
| 16.10.24 | 36 / 16 | |
| 16.10.23 | 36 / 16 | |
| 16.10.22 | 36 / 16 | |
| 16.10.21 | 36 / 16 | |
| 16.10.20 | 36 / 16 | |
| 16.10.19 | 36 / 16 | |
| 16.10.18 | 36 / 16 | |
| 16.10.17 | 36 / 16 | |
| 16.10.16 | 36 / 16 | |
| 16.10.15 | 36 / 16 | |
| 16.10.14 | 36 / 16 | |
| 16.10.13 | 36 / 16 | |
| 16.10.12 | 36 / 16 | |
| 16.10.11 | 36 / 16 | |
| 16.10.10 | 36 / 16 | |
| 16.10.9 | 36 / 16 | |
| 16.10.8 | 36 / 16 | |
| 16.10.7 | 36 / 16 | |
| 16.10.6 | 36 / 16 | |
| 16.10.5 | 36 / 16 | |
| 16.10.4 | 36 / 16 | |
| 16.10.3 | 36 / 16 | |
| 16.10.2 | 36 / 16 | |
| 16.10.1 | 36 / 16 | |
| 16.10.0 | 36 / 16 | |
| 16.9.8 | 36 / 16 | |
| 16.9.7 | 36 / 16 | |
| 16.9.6 | 36 / 16 | |
| 16.9.5 | 36 / 16 | |
| 16.9.4 | 36 / 16 | |
| 16.9.3 | 36 / 16 | |
| 16.9.2 | 36 / 16 | |
| 16.9.1 | 36 / 16 | |
| 16.9.0 | 36 / 16 | |
| 16.8.6 | 35 / 16 | |
| 16.8.5 | 35 / 16 | |
| 16.8.4 | 35 / 16 | |
| 16.8.3 | 35 / 16 | |
| 16.8.2 | 35 / 16 | |
| 16.8.1 | 35 / 16 | |
| 16.8.0 | 35 / 16 | |
| 16.7.32 | 35 / 16 | |
| 16.7.31 | 35 / 16 | |
| 16.7.30 | 35 / 16 | |
| 16.7.29 | 35 / 16 | |
| 16.7.28 | 35 / 16 | |
| 16.7.27 | 35 / 16 | |
| 16.7.26 | 35 / 16 | |
| 16.7.25 | 35 / 16 | |
| 16.7.24 | 35 / 16 | |
| 16.7.23 | 35 / 16 | |
| 16.7.22 | 35 / 16 | |
| 16.7.21 | 35 / 16 | |
| 16.7.20 | 35 / 16 | |
| 16.7.19 | 35 / 16 | |
| 16.7.18 | 35 / 16 | |
| 16.7.17 | 35 / 16 | |
| 16.7.16 | 35 / 17 | |
| 16.7.15 | 35 / 17 | |
| 16.7.14 | 35 / 17 | |
| 16.7.13 | 35 / 17 | |
| 16.7.12 | 35 / 17 | |
| 16.7.11 | 35 / 17 | |
| 16.7.10 | 35 / 17 | |
| 16.7.9 | 35 / 17 | |
| 16.7.8 | 35 / 17 | |
| 16.7.7 | 35 / 17 | |
| 16.7.6 | 35 / 17 | |
| 16.7.5 | 35 / 17 | |
| 16.7.4 | 35 / 17 | |
| 16.7.3 | 35 / 17 | |
| 16.7.2 | 35 / 17 | |
| 16.7.1 | 35 / 17 | |
| 16.7.0 | 35 / 17 | |
| 16.6.0 | 35 / 17 | |
| 16.5.19 | 35 / 17 | |
| 16.5.18 | 35 / 17 | |
| 16.5.17 | 35 / 17 | |
| 16.5.16 | 35 / 17 | |
| 16.5.15 | 35 / 17 | |
| 16.5.14 | 35 / 17 | |
| 16.5.13 | 35 / 17 | |
| 16.5.12 | 35 / 17 | |
| 16.5.11 | 35 / 17 | |
| 16.5.10 | 35 / 17 |
v16.10.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.10.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.10.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.10.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.10.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.10.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.10.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.10.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.10.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.10.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.10.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.10.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.10.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.10.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.9.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.9.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.8.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.8.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.5.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.5.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.5.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.5.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.5.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.5.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.5.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.5.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.5.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.5.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.