← Home

@itentialopensource/adapter-kafkav2

npm Repository Homepage

Itential adapter to connect to kafka

10
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 PlatformAutomationIntegrationAdapterNotificationMessagingKafkav2Pre-Release

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): kafka-lz4-lite and kafkajs-snappy are Kafka compression codecs; contextually appropriate for a Kafka adapter. ai
provenance no-provenance AI (provenance): Established Itential org package; lack of Sigstore provenance is consistent across all versions and not a disqualifier here. ai
dependencies unvetted-dep:kafka-lz4-lite AI (dependencies): Legitimate Kafka compression codec library; expected dependency for a Kafka adapter. ai
dependencies unvetted-dep:kafkajs-snappy AI (dependencies): Legitimate KafkaJS Snappy compression plugin; expected dependency for a Kafka adapter. ai
dependencies unvetted-dep:avro-schema-registry AI (dependencies): Legitimate Avro schema registry client; expected for Kafka Avro serialization use cases. ai
phantom-deps phantom-dep:mocha AI (phantom-deps): mocha is a test runner referenced in scripts, not imported in source; stable false positive. ai
install-scripts install-script:preinstall AI (install-scripts): Itential adapter framework uses preinstall setup.js for hook registration; consistent across all adapter versions. ai
phantom-deps phantom-dep:json-query AI (phantom-deps): json-query used in adapter logic via config references; stable false positive for this package. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic requires use path.join(__dirname, ...) with hardcoded relative paths — not user-controlled. ai
semgrep semgrep:child-process-import AI (semgrep): child_process used in packaging utility (packModificationScript.js), not in runtime adapter code. ai
phantom-deps phantom-dep:ajv AI (phantom-deps): ajv is a declared dependency used via config/schema validation, not direct import; stable false positive. ai
phantom-deps phantom-dep:avsc AI (phantom-deps): avsc used indirectly via avro-schema-registry; stable false positive for this adapter. ai

Versions (showing 10 of 10)

Version Deps Published
1.0.2 14 / 6
1.0.1 14 / 6
1.0.0 14 / 6
0.26.7 14 / 6
0.26.6 14 / 6
0.26.5 12 / 6
0.26.4 12 / 6
0.26.3 12 / 6
0.26.2 12 / 6
0.26.1 12 / 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

1 finding
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.26.7

1 finding
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.26.6

1 finding
INFO No provenance attestation provenance

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

v0.26.5

1 finding
INFO No provenance attestation provenance

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

v0.26.4

1 finding
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.26.3

1 finding
INFO No provenance attestation provenance

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

v0.26.2

1 finding
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.26.1

1 finding
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.