← Home

@itentialopensource/adapter-gitlab

npm Repository Homepage

This adapter integrates with system described as: gitlab.

3
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 PlatformAutomationIntegrationAdapterDevOpsNetOpsGitlabPre-Release

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Established Itential adapter org with 454 approved packages; dormancy consistent with infrequent maintenance cycles. ai
semgrep semgrep:child-process-import AI (semgrep): child_process used for adapter setup/migration utilities; consistent with Itential adapter framework pattern. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require loads local JSON config files (__dirname-anchored); not arbitrary module loading. ai
install-scripts install-script:preinstall AI (install-scripts): Itential adapter framework uses preinstall for setup scaffolding; stable pattern across all versions of this package family. ai
phantom-deps phantom-dep:prompts AI (phantom-deps): prompts used in interactive utility scripts, not main adapter code; stable false positive for this package. ai
phantom-deps phantom-dep:mocha-param AI (phantom-deps): mocha-param referenced in test config files; phantom-dep heuristic fires because it's not directly imported in main source. ai
phantom-deps phantom-dep:ping AI (phantom-deps): ping is used in connectivity/healthcheck utility scripts referenced in package.json scripts, not directly imported in main code. ai

Versions (showing 3 of 3)

Version Deps Published
1.0.2 15 / 6
1.0.1 15 / 6
1.0.0 15 / 6

v1.0.2

1 finding
LOW No provenance attestation provenance

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

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.