← Home

@edirect/audit-instrumentation-express

npm

Express.js auto-instrumentation for the eDirect Audit system. Automatically extracts request context (client IP, origin URL, session ID) from incoming Express requests and injects it into audit events — so you don't have to pass this data manually in ever

13
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

samuelbolttechrobertoakangmathaisedirectamorimricardo.coelhoadailson.bolttechlayunne-bolttechdavid.pereirapaulomarchibruno.gomesplinio.altoeiquirino.bolttechjoaoferreirabolttechlukaspiccinibtdiogo.bolttechpalvares_bolttechrafael.jourdanpauloazevedo-edguilherme_benedetiandsfranboltdanielkhalebbatistadiogopinheiro.bolttechrodrigo.pradoherberts.fortunamatheus.maciel.bolttechpedro.leite.bolttechandrerocha0510jozimarleandronovaesbolttech

Versions (showing 13 of 13)

Version Deps Published
11.0.56 4 / 2
11.0.55 4 / 2
11.0.54 4 / 2
11.0.53 4 / 2
11.0.52 4 / 2
11.0.49 4 / 2
11.0.48 4 / 2
11.0.43 4 / 2
11.0.41 4 / 2
11.0.40 4 / 2
11.0.39 4 / 2
11.0.37 4 / 2
11.0.36 4 / 2

v11.0.56

1 finding
LOW No provenance attestation provenance

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

v11.0.55

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.

v11.0.54

1 finding
LOW No provenance attestation provenance

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

v11.0.53

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.

v11.0.52

1 finding
LOW No provenance attestation provenance

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

v11.0.49

1 finding
LOW No provenance attestation provenance

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

v11.0.48

1 finding
LOW No provenance attestation provenance

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

v11.0.43

1 finding
LOW No provenance attestation provenance

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

v11.0.41

1 finding
LOW No provenance attestation provenance

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

v11.0.40

1 finding
LOW No provenance attestation provenance

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

v11.0.39

1 finding
LOW No provenance attestation provenance

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

v11.0.37

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.

v11.0.36

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.