@itentialopensource/adapter-kubernetes
This adapter integrates with system described as: kubernetes.
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 script pattern; consistent across all versions of this org's adapters. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): ping is a utility dep used by adapter framework tooling, not directly imported in main source. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): prompts used by interactive setup/migration utilities, not main adapter code. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): mocha-param is a test utility; not imported in main source but used in test scripts. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process usage in adapterBase.js is standard for Itential adapter framework connection management. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require resolves local sampleProperties.json via __dirname; not arbitrary user input. | ai |
v1.0.2
5 findingsScript: node utils/setup.js
Declared in package.json dependencies but never imported in source code. Phantom dependencies may exist solely to execute install scripts or inject transitive malicious code. This was the exact attack vector in the axios compromise (plain-crypto-js).
Declared in package.json dependencies but never imported in source code. Phantom dependencies may exist solely to execute install scripts or inject transitive malicious code. This was the exact attack vector in the axios compromise (plain-crypto-js).
Declared in package.json dependencies but never imported in source code. Phantom dependencies may exist solely to execute install scripts or inject transitive malicious code. This was the exact attack vector in the axios compromise (plain-crypto-js).
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
5 findingsScript: node utils/setup.js
Declared in package.json dependencies but never imported in source code. Phantom dependencies may exist solely to execute install scripts or inject transitive malicious code. This was the exact attack vector in the axios compromise (plain-crypto-js).
Declared in package.json dependencies but never imported in source code. Phantom dependencies may exist solely to execute install scripts or inject transitive malicious code. This was the exact attack vector in the axios compromise (plain-crypto-js).
Declared in package.json dependencies but never imported in source code. Phantom dependencies may exist solely to execute install scripts or inject transitive malicious code. This was the exact attack vector in the axios compromise (plain-crypto-js).
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.