@itentialopensource/adapter-bitbucket
This adapter integrates with system described as: bitbucket.
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 org adapter; publisher has 454 approved packages and diff shows no suspicious changes. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Fires on path.join(__dirname, 'adapterBase.js') — effectively a static path, not arbitrary module loading. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used for adapter tooling utilities (healthcheck, connectivity); consistent with documented adapter functionality. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Standard Itential adapter setup script pattern; stable across all versions of this package family. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): prompts used in setup/migration utilities referenced via config; stable false positive. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): mocha-param used in test files referenced via config; stable false positive. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): ping is a declared runtime dep used in adapter connectivity checks via config; stable false positive. | ai |
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.