← Home

@itentialopensource/adapter-checkpoint_gaia

npm Repository Homepage

This adapter integrates with system described as: gaiaApi-1.6.

4
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 PlatformAutomationIntegrationAdaptercheckpoint_gaiaPre-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 helper dependency; not a runtime risk for this adapter package. ai
semgrep semgrep:dynamic-require AI (semgrep): Fires on path.join(__dirname, 'adapterBase.js') — static path construction, not truly dynamic module loading. ai
semgrep semgrep:child-process-import AI (semgrep): Standard Itential adapter pattern for running connectivity/health checks via execSync/spawnSync. ai
install-scripts install-script:preinstall AI (install-scripts): Itential adapter pattern; preinstall runs utils/setup.js for git hooks setup, consistent across all adapter versions. 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 utility referenced in test config files, not directly imported in source. ai
phantom-deps phantom-dep:ping AI (phantom-deps): ping is a declared runtime dep used in adapter connectivity utilities, referenced in config files as expected. ai

Versions (showing 4 of 4)

Version Deps Published
1.0.3 15 / 6
1.0.1 15 / 6
1.0.0 15 / 6
0.5.0 15 / 6

v1.0.3

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.

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