@kafkajs/confluent-schema-registry
2
Versions
—
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
gitHead linked
Maintainers
tuliosengervallnevon
Keywords
confluent schema registrykafka
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions (CI/CD automation), corroborated by SLSA provenance attestation via Sigstore. This is a legitimate migration to automated releases for the kafkajs org. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long dormancy followed by GitHub Actions publish with SLSA attestation indicates legitimate project revival, not account takeover. Matches kafkajs org repo. | ai | |
| provenance | no-provenance | AI (provenance): Established kafkajs ecosystem package; lack of Sigstore provenance is common and not a risk signal for this well-known library. | ai |
v4.0.8
2 findings
HIGH
Publisher changed: nevon → GitHub Actions (on 2026-03-30)
provenance
This version was published by a different npm account than previous versions on 2026-03-30. This could indicate a legitimate maintainer transition or an account compromise.
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.9.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.