← Home

@itentialopensource/adapter-bitbucket_server

This adapter integrates with system described as: api.

6
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 PlatformAutomationIntegrationAdapterbitbucket_serverPre-Release

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:mocha-param AI (dependencies): mocha-param is a test utility dependency stable across versions of this adapter package; not a runtime risk. ai
semgrep semgrep:child-process-import AI (semgrep): child_process used in adapter framework base class for legitimate system operations; stable pattern across Itential adapters. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require resolves local config/property files by path; not arbitrary user input. Stable pattern in this adapter framework. ai
install-scripts install-script:preinstall AI (install-scripts): Standard Itential adapter setup script pattern; consistent across all versions of this package family. ai
phantom-deps phantom-dep:prompts AI (phantom-deps): prompts used in interactive setup/migration utilities; phantom-dep heuristic false positive. ai
phantom-deps phantom-dep:mocha-param AI (phantom-deps): mocha-param used in test files via mocha runner; not directly imported in main code. False positive. ai
phantom-deps phantom-dep:ping AI (phantom-deps): ping is used in connectivity/troubleshoot utilities referenced in scripts; phantom-dep heuristic false positive. ai

Versions (showing 6 of 6)

Version Deps Published
2.0.3 15 / 6
2.0.1 15 / 6
2.0.0 15 / 6
1.7.3 15 / 6
1.7.2 15 / 6
1.5.1 15 / 6

v2.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.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.

v2.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.

v1.7.3

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.7.2

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.5.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.