@itentialopensource/adapter-jenkins
This adapter integrates with system described as: jenkins.
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Established Itential adapter org with 454 approved packages; inactivity gap is not indicative of takeover given consistent package structure. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Path-based require with __dirname is not arbitrary module loading; stable pattern in Itential adapter framework. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): execSync/spawnSync used for connectivity/healthcheck utilities in Itential adapter base; documented framework behavior. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Standard Itential adapter setup script pattern; consistent across all versions of this adapter family. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): prompts used in setup/utility scripts referenced via config, not direct import in main code. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): mocha-param is a test dependency referenced in test config files, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): ping is a declared runtime dependency used in adapter connectivity checks via config, not direct import. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.0.2 | 15 / 6 | |
| 1.0.1 | 15 / 6 | |
| 1.0.0 | 15 / 6 | |
| 0.9.3 | 15 / 6 | |
| 0.9.2 | 15 / 6 | |
| 0.9.1 | 15 / 6 | |
| 0.8.0 | 15 / 6 | |
| 0.7.1 | 15 / 6 | |
| 0.7.0 | 15 / 6 |
v1.0.2
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.
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.9.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.9.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.
v0.9.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.8.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.7.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.7.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.