yak0/nest-event
44.8
Weak · 21 September 2026
167
lines of production code
TypeScript
primary language
4
measurements over time
What this system is
This system is a NestJS library that implements an event-driven architecture to facilitate inter-module communication without direct imports. It provides an internal event emitter with support for named emitters and uses decorators to bind methods to specific event handlers. The codebase includes configuration files for TypeScript, linting, and CI, along with placeholder test structures.
Features
Initial release of NestEvent module for event-driven architecture
The library introduces a new \NestEventModule\ that enables event-driven communication within NestJS applications. It provides decorators (\@On\, \@From\, \@Emitter\, \@InjectNestEvent\) to bind methods to specific event emitters and allows direct emission of events via the \NestEventEmitter\ service. The module automatically discovers controllers and providers, binding decorated methods to the corresponding event emitters, with support for named emitters and a default fallback.
src · high confidence
Initial release of the Nest Event library
This change introduces the initial version of the 'nest-event' library, a module for the Nest.js framework that enables communication between modules without direct imports. It provides an internal event emitter and supports multiple named emitters, allowing developers to organize event handlers using decorators like @On and @From. The release includes configuration files for TypeScript (tsconfig.json), linting (tslint.json), code formatting (.prettierrc), CI (.travis.yml), and build scripts (build.sh), alongside the main README documentation.
(repo-wide) · high confidence
Test coverage
Added placeholder file in test directory
A .gitkeep file was added to the test directory, ensuring the directory is tracked by version control.
test · high confidence
Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
How this codebase got here
Score
- CAI 50 → 45 (-5.5)
- Rubric changed (rubric-2026.08.19 → rubric-2026.09.15) — scores are not directly comparable.
Lenses
- Code Health 98 → 99 (+1.4)
- Architecture 69 → 69 (+0.0)
- Maturity 59 → 59 (+0.0)
- Readiness 29 → 23 (-5.5)
- Security 75 → 60 (-15.0)
Resolved (56)
- Critical CVE: [GHSA redacted] (package-lock.json)
- Critical CVE: [GHSA redacted] (package-lock.json)
- Critical CVE: [GHSA redacted] (package-lock.json)
- Critical CVE: [GHSA redacted] (package-lock.json)
- Critical CVE: [GHSA redacted] (package-lock.json)
- Critical CVE: [GHSA redacted] (package-lock.json)
- Critical CVE: [GHSA redacted] (package-lock.json)
- Critical CVE: [GHSA redacted] (package-lock.json)
- Critical CVE: [GHSA redacted] (package-lock.json)
- Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
- High CVE: [GHSA redacted] (package-lock.json)
- High CVE: [GHSA redacted] (package-lock.json)
- High CVE: [GHSA redacted] (package-lock.json)
- High CVE: [GHSA redacted] (package-lock.json)
- High CVE: [GHSA redacted] (package-lock.json)
- High CVE: [GHSA redacted] (package-lock.json)
- High CVE: [GHSA redacted] (package-lock.json)
- High CVE: [GHSA redacted] (package-lock.json)
- High CVE: [GHSA redacted] (package-lock.json)
- High CVE: [GHSA redacted] (package-lock.json)
- …and 36 more
New (54)
- Critical CVE: [GHSA redacted] (package-lock.json)
- Critical CVE: [GHSA redacted] (package-lock.json)
- Critical CVE: [GHSA redacted] (package-lock.json)
- Critical CVE: [GHSA redacted] (package-lock.json)
- Critical CVE: [GHSA redacted] (package-lock.json)
- Critical CVE: [GHSA redacted] (package-lock.json)
- Critical CVE: [GHSA redacted] (package-lock.json)
- Critical CVE: [GHSA redacted] (package-lock.json)
- Critical CVE: [GHSA redacted] (package-lock.json)
- Dependency hygiene PARTLY measured — npm pinning read, dependency currency not (the committed lockfile is in a format this engine cannot resolve)
- Documentation: no architecture or design documentation (README.md)
- High CVE: [GHSA redacted] (package-lock.json)
- High CVE: [GHSA redacted] (package-lock.json)
- High CVE: [GHSA redacted] (package-lock.json)
- High CVE: [GHSA redacted] (package-lock.json)
- High CVE: [GHSA redacted] (package-lock.json)
- High CVE: [GHSA redacted] (package-lock.json)
- High CVE: [GHSA redacted] (package-lock.json)
- High CVE: [GHSA redacted] (package-lock.json)
- High CVE: [GHSA redacted] (package-lock.json)
- …and 34 more
Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
yak0/nest-event was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.
About this page
- The score is its most recent published measurement, taken on 21 September 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit b323398ecb08dcf82e3ec2595fbf836b12c2f32c — the exact code this score is about.
- Scored under rubric-2026.09.15 — the same rubric and the same method as every other entry in this index.
- Measured by watchdog.canine.dev using codehealth-analyzer preprod-b84573e22831.