NPM LIBRARY
@opuscapita/kafka-client
Official package-registry history. This page does not infer support or EOL from release activity.
- Versions indexed
- 14
- Latest version activity
- 2.0.2
- Latest registry signal
- Published
- Last synchronized
- 26 Sep 2026
Authoritative registry
Version entries link to the official registry catalogue event that supplied the record.
Open package on npm ↗Lifecycle interpretation
Publication or deletion in a package registry is a distribution signal, not a promise of maintenance or security support. Any verified publisher EOL boundary remains in the main lifecycle catalogue.
Package-version activity
Newest official registry events first.
| Version | Registry event | Signal | Release notes | Evidence |
|---|---|---|---|---|
| 2.0.2 | 17 Sep 2026 | PUBLISHED | Checked, none published | Official event ↗ |
| 2.0.1 | 25 Oct 2023 | PUBLISHED | Checked, none published | Official event ↗ |
| 2.0.0 | 2 Oct 2023 | PUBLISHED | Checked, none published | Official event ↗ |
| 1.0.11 | 23 Jul 2021 | DEPRECATEDConsider using vanilla KafkaJS instead. This library is not used, not maintained for a long time and has several serious limitations including autocommit (for highly reliable systems you probably prefer better protection from lost messages), execution of consumers in separate calls (making it more difficult to handle full batch together for bound messages), lack of solid documentation and possibly hiding some kafkajs interfaces from you | Checked, none published | Official event ↗ |
| 1.0.10 | 29 Aug 2019 | DEPRECATEDConsider using vanilla KafkaJS instead. This library is not used, not maintained for a long time and has several serious limitations including autocommit (for highly reliable systems you probably prefer better protection from lost messages), execution of consumers in separate calls (making it more difficult to handle full batch together for bound messages), lack of solid documentation and possibly hiding some kafkajs interfaces from you | Checked, none published | Official event ↗ |
| 1.0.8 | 9 Aug 2019 | DEPRECATEDConsider using vanilla KafkaJS instead. This library is not used, not maintained for a long time and has several serious limitations including autocommit (for highly reliable systems you probably prefer better protection from lost messages), execution of consumers in separate calls (making it more difficult to handle full batch together for bound messages), lack of solid documentation and possibly hiding some kafkajs interfaces from you | Checked, none published | Official event ↗ |
| 1.0.7 | 29 Jul 2019 | DEPRECATEDConsider using vanilla KafkaJS instead. This library is not used, not maintained for a long time and has several serious limitations including autocommit (for highly reliable systems you probably prefer better protection from lost messages), execution of consumers in separate calls (making it more difficult to handle full batch together for bound messages), lack of solid documentation and possibly hiding some kafkajs interfaces from you | Checked, none published | Official event ↗ |
| 1.0.6 | 24 Jul 2019 | DEPRECATEDConsider using vanilla KafkaJS instead. This library is not used, not maintained for a long time and has several serious limitations including autocommit (for highly reliable systems you probably prefer better protection from lost messages), execution of consumers in separate calls (making it more difficult to handle full batch together for bound messages), lack of solid documentation and possibly hiding some kafkajs interfaces from you | Checked, none published | Official event ↗ |
| 1.0.5 | 24 Jul 2019 | DEPRECATEDConsider using vanilla KafkaJS instead. This library is not used, not maintained for a long time and has several serious limitations including autocommit (for highly reliable systems you probably prefer better protection from lost messages), execution of consumers in separate calls (making it more difficult to handle full batch together for bound messages), lack of solid documentation and possibly hiding some kafkajs interfaces from you | Checked, none published | Official event ↗ |
| 1.0.4 | 24 Jul 2019 | DEPRECATEDConsider using vanilla KafkaJS instead. This library is not used, not maintained for a long time and has several serious limitations including autocommit (for highly reliable systems you probably prefer better protection from lost messages), execution of consumers in separate calls (making it more difficult to handle full batch together for bound messages), lack of solid documentation and possibly hiding some kafkajs interfaces from you | Checked, none published | Official event ↗ |
| 1.0.3 | 12 Jul 2019 | DEPRECATEDConsider using vanilla KafkaJS instead. This library is not used, not maintained for a long time and has several serious limitations including autocommit (for highly reliable systems you probably prefer better protection from lost messages), execution of consumers in separate calls (making it more difficult to handle full batch together for bound messages), lack of solid documentation and possibly hiding some kafkajs interfaces from you | Checked, none published | Official event ↗ |
| 1.0.2 | 11 Jul 2019 | DEPRECATEDConsider using vanilla KafkaJS instead. This library is not used, not maintained for a long time and has several serious limitations including autocommit (for highly reliable systems you probably prefer better protection from lost messages), execution of consumers in separate calls (making it more difficult to handle full batch together for bound messages), lack of solid documentation and possibly hiding some kafkajs interfaces from you | Checked, none published | Official event ↗ |
| 1.0.1 | 8 Jul 2019 | DEPRECATEDConsider using vanilla KafkaJS instead. This library is not used, not maintained for a long time and has several serious limitations including autocommit (for highly reliable systems you probably prefer better protection from lost messages), execution of consumers in separate calls (making it more difficult to handle full batch together for bound messages), lack of solid documentation and possibly hiding some kafkajs interfaces from you | Checked, none published | Official event ↗ |
| 1.0.0 | 8 Jul 2019 | DEPRECATEDConsider using vanilla KafkaJS instead. This library is not used, not maintained for a long time and has several serious limitations including autocommit (for highly reliable systems you probably prefer better protection from lost messages), execution of consumers in separate calls (making it more difficult to handle full batch together for bound messages), lack of solid documentation and possibly hiding some kafkajs interfaces from you | Checked, none published | Official event ↗ |