← Home

@itentialopensource/adapter-tcpwave

This adapter integrates with system described as: tcpwaveRestapiStore.

2
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 PlatformAutomationIntegrationAdapterInventoryTCPWavePre-Release

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:preinstall AI (install-scripts): Standard Itential adapter preinstall pattern; runs local setup.js, consistent across all versions of this adapter family. ai
semgrep semgrep:child-process-import AI (semgrep): child_process usage is part of the Itential adapter-utils framework pattern; stable across versions. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require loads local sampleProperties.json config; not arbitrary module loading, stable pattern for this package. ai
phantom-deps phantom-dep:ping AI (phantom-deps): ping is a declared runtime dep used in adapter connectivity checks; phantom-dep heuristic false positive. ai
phantom-deps phantom-dep:prompts AI (phantom-deps): prompts used in interactive setup utilities; phantom-dep heuristic false positive for this adapter. ai
phantom-deps phantom-dep:mocha-param AI (phantom-deps): mocha-param used in test config files; phantom-dep heuristic false positive. ai

Versions (showing 2 of 2)

Version Deps Published
1.0.1 15 / 6
1.0.0 15 / 6

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.