← Home

@itentialopensource/adapter-chatgpt

npm Repository Homepage

This adapter integrates with system described as: Chatgpt.

7
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 PlatformAutomationIntegrationAdapterchatgptPre-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-only dependency used for parameterized mocha tests; no runtime exposure. ai
semgrep semgrep:dynamic-require AI (semgrep): Fires on path.join(__dirname, 'adapterBase.js') — static path construction, not truly dynamic; stable false positive for this adapter pattern. ai
semgrep semgrep:child-process-import AI (semgrep): child_process used for adapter tooling/setup utilities; consistent pattern across Itential adapter packages. ai
install-scripts install-script:preinstall AI (install-scripts): Standard Itential adapter preinstall pattern (node utils/setup.js); consistent across all versions of this package family. ai
phantom-deps phantom-dep:prompts AI (phantom-deps): Used in config/test files rather than direct import; stable false positive for this adapter. ai
phantom-deps phantom-dep:mocha-param AI (phantom-deps): Test dependency referenced in config files; stable false positive for this adapter. ai
phantom-deps phantom-dep:ping AI (phantom-deps): Used in config/test files rather than direct import; stable false positive for this adapter. ai

Versions (showing 7 of 7)

Version Deps Published
1.0.3 15 / 6
1.0.2 15 / 6
1.0.1 15 / 6
0.6.2 15 / 6
0.5.1 15 / 6
0.5.0 15 / 6
0.4.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.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.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.

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

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

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.

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