@itentialopensource/adapter-aws_ec2
This adapter integrates with system described as: Aws_Ec2.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:preinstall | AI (install-scripts): Standard Itential adapter setup hook (node utils/setup.js); consistent across all versions of this adapter family. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process usage is part of the adapterBase.js framework boilerplate; stable across all Itential adapter versions. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require resolves local JSON config files via __dirname; not arbitrary user input. Stable pattern in this adapter family. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): Used in adapter connectivity utilities; referenced in config files as documented. | ai | |
| phantom-deps | phantom-dep:jssha | AI (phantom-deps): Used for auth signing in adapter utils; referenced in config files as documented. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): Used in interactive setup/migration utilities; referenced in config files as documented. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): Test dependency referenced in test config files; stable false positive for this adapter. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.0.3 | 16 / 6 | |
| 1.0.2 | 16 / 6 | |
| 1.0.1 | 16 / 6 | |
| 1.0.0 | 16 / 6 |
v1.0.3
2 findingsScript: node utils/setup.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
2 findingsScript: node utils/setup.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
2 findingsScript: node utils/setup.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
2 findingsScript: node utils/setup.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.