@edirect/nest-app No license 33 versions

@edirect/nest-app

npm

Opinionated NestJS application bootstrapper for eDirect services. Provides a single `bootstrap()` function that wires up NestJS with eDirect conventions: environment loading, Swagger documentation, global pipes/filters, session, CORS, XML body parsing, an

33

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

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:class-validator	AI (phantom-deps): class-validator is a declared runtime dep used via NestJS decorators/config, not direct imports; stable false positive for this package.	ai	2026/05/17

Versions (showing 33 of 33)

Version	Deps	Published
11.0.56	21 / 6	2026-04-19
11.0.55	21 / 6	2026-04-16
11.0.54	21 / 6	2026-04-09
11.0.53	21 / 6	2026-04-01
11.0.52	21 / 6	2026-03-25
11.0.49	21 / 6	2026-03-11
11.0.48	21 / 6	2026-03-04
11.0.43	21 / 6	2026-01-29
11.0.41	21 / 6	2026-01-26
11.0.40	21 / 6	2026-01-16
11.0.39	21 / 6	2026-01-08
11.0.37	21 / 6	2026-01-07
11.0.36	21 / 6	2025-12-10
11.0.35	21 / 6	2025-12-02
11.0.34	21 / 6	2025-11-12
11.0.33	21 / 6	2025-10-24
11.0.30	20 / 6	2025-10-10
11.0.26	21 / 6	2025-09-03
11.0.25	21 / 6	2025-08-26
11.0.23	21 / 6	2025-08-22
11.0.22	21 / 6	2025-08-22
11.0.21	21 / 6	2025-08-22
11.0.20	21 / 6	2025-08-22
11.0.19	20 / 6	2025-08-22
11.0.15	20 / 7	2025-08-21
11.0.14	20 / 7	2025-08-20
11.0.13	20 / 7	2025-08-20
11.0.12	19 / 7	2025-08-20
11.0.11	19 / 7	2025-08-20
11.0.10	19 / 7	2025-08-20
11.0.9	19 / 7	2025-08-20
11.0.8	18 / 7	2025-08-20
11.0.7	18 / 7	2025-08-20

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. Consider requesting the maintainer enable provenance via CI/CD.

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. Consider requesting the maintainer enable provenance via CI/CD.

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.

v11.0.35

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.34

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.33

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.30

1 finding

LOW No provenance attestation provenance

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

v11.0.26

1 finding

LOW No provenance attestation provenance

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

v11.0.25

1 finding

LOW No provenance attestation provenance

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

v11.0.23

1 finding

LOW No provenance attestation provenance

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

v11.0.22

1 finding

LOW No provenance attestation provenance

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

v11.0.21

1 finding

LOW No provenance attestation provenance

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

v11.0.20

1 finding

LOW No provenance attestation provenance

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

v11.0.19

1 finding

LOW No provenance attestation provenance

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

v11.0.15

1 finding

LOW No provenance attestation provenance

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

v11.0.14

1 finding

LOW No provenance attestation provenance

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

v11.0.13

1 finding

LOW No provenance attestation provenance

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

v11.0.12

1 finding

LOW No provenance attestation provenance

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

v11.0.11

1 finding

LOW No provenance attestation provenance

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

v11.0.10

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.9

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.8

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.7

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.