@itentialopensource/adapter-azure_devops
This adapter integrates with system described as: Azure DevOps.
2
Versions
Apache-2.0
License
Yes
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
jared.obrienjohnpolanskyzack.strulovitchitential-ciandyknaebelishitaprakash
Keywords
ItentialItential PlatformAutomationIntegrationAdapterDevOpsNetOpsAzureDevOpsPipelinesPre-Release
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; stable across all versions of this package family. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require used to load adapterBase.js by path — standard adapter framework pattern, not arbitrary user input. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used for adapter utility/migration scripts; consistent with Itential adapter framework across all versions. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): ping is used in connectivity/healthcheck utility scripts referenced in config; stable false positive for this adapter. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): prompts used in interactive setup/migration utilities; referenced in config files as expected. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): mocha-param is a test dependency referenced in test config files; stable false positive. | ai |
v1.0.1
2 findings
HIGH
Package has 'preinstall' script
install-scripts
Script: node utils/setup.js
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
2 findings
HIGH
Package has 'preinstall' script
install-scripts
Script: node utils/setup.js
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.