@itentialopensource/adapter-aws_s3
This adapter integrates with system described as: Aws_S3.
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 pattern; setup.js installs git hooks, not arbitrary remote code. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Itential adapter framework uses path.join(__dirname, ...) dynamic requires for known local files — not user-controlled. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): adapterBase.js uses execSync/spawnSync for adapter utility operations; stable pattern across Itential adapter family. | ai | |
| phantom-deps | phantom-dep:aws-sdk | AI (phantom-deps): aws-sdk is a declared runtime dependency used via config-driven loading in this AWS S3 adapter. | ai | |
| phantom-deps | phantom-dep:aws4 | AI (phantom-deps): aws4 is a declared runtime dependency for AWS request signing; loaded via adapter config. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): ping is a declared dependency used in connectivity/healthcheck utilities. | ai | |
| phantom-deps | phantom-dep:esprima | AI (phantom-deps): esprima is a declared dependency used in adapter migration/analysis utilities. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): prompts is a declared dependency used in interactive setup/migration utilities. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): mocha-param is a declared test dependency; phantom-dep false positive for test-only usage. | ai |
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.
v0.12.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.