@edirect/audit-nestjs
NestJS integration for the eDirect Audit system. Provides a configurable `AuditModule` and a request-scoped `AuditService` that automatically extracts trace/session context from Express requests and dispatches audit events via a configurable exporter.
Supply chain provenance
Status for the latest visible version.
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
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 11.0.56 | 7 / 1 | |
| 11.0.55 | 7 / 1 | |
| 11.0.54 | 7 / 1 | |
| 11.0.53 | 7 / 1 | |
| 11.0.52 | 7 / 1 | |
| 11.0.49 | 7 / 1 | |
| 11.0.48 | 7 / 1 | |
| 11.0.43 | 7 / 1 | |
| 11.0.41 | 7 / 1 | |
| 11.0.40 | 7 / 1 | |
| 11.0.39 | 6 / 1 | |
| 11.0.37 | 6 / 1 | |
| 11.0.36 | 6 / 1 |
v11.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.