← Home

@itentialopensource/adapter-github

npm Repository Homepage

This adapter integrates with system described as: github.

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 PlatformAutomationIntegrationAdapterDevOpsNetOpsgithubPre-Release

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Established Itential org package with trusted publisher history; no material changes from prior version. ai
semgrep semgrep:child-process-import AI (semgrep): Adapter framework legitimately uses child_process for system integration; stable pattern across all versions. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require loads local config/properties files by path; not arbitrary user input. Stable adapter pattern. ai
install-scripts install-script:preinstall AI (install-scripts): Itential adapter pattern; preinstall runs local setup.js, not remote code. Stable across versions. ai
phantom-deps phantom-dep:prompts AI (phantom-deps): prompts used in interactive utility scripts, not main module imports. Stable false positive for this adapter. ai
phantom-deps phantom-dep:mocha-param AI (phantom-deps): mocha-param is a test dependency referenced in test config files, not directly imported. Stable false positive. ai
phantom-deps phantom-dep:ping AI (phantom-deps): ping is a declared runtime dep used in config/connectivity 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.