@itentialopensource/adapter-aws_organizations
This adapter integrates with system described as: AWS Organizations.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:mocha-param | AI (dependencies): mocha-param is a test-only dependency used across all Itential adapter packages; stable false positive for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in adapter.js loads adapterBase.js via path.join — deterministic path, not user-controlled. Framework pattern stable across versions. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): execSync/spawnSync in adapterBase.js is part of the Itential adapter framework; stable pattern across all versions. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Standard Itential adapter setup script pattern; stable across all versions of this adapter family. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): prompts referenced in config files; stable false positive for this adapter. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): mocha-param referenced in test config files; stable false positive for this adapter. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): ping is referenced in config/test files per phantom-dep note; stable false positive for this adapter. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.0.3 | 15 / 6 | |
| 1.0.1 | 15 / 6 | |
| 0.6.4 | 15 / 6 | |
| 0.6.3 | 15 / 6 | |
| 0.6.1 | 15 / 6 | |
| 0.6.0 | 15 / 6 | |
| 0.5.1 | 15 / 6 | |
| 0.4.0 | 15 / 6 |
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
v0.6.4
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.6.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.
v0.6.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.
v0.6.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.5.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.
v0.4.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.