← Home

@nestjs/microservices

npm Repository Homepage
6
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

nestjscore

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:dynamic-require AI (semgrep): Optional proto-loader selection pattern; stable and documented across NestJS microservices versions. ai
semgrep semgrep:api-obfuscation-reflect AI (semgrep): Standard Proxy trap using Reflect.get() in gRPC server; not obfuscation. ai
bogus-package bogus-package AI (bogus-package): NestJS official package; README link density reflects framework docs, not a phishing farm. ai

Versions (showing 6 of 6)

Version Deps Published
11.1.24 2 / 2
11.1.23 2 / 2
11.1.22 2 / 2
11.1.21 2 / 2
11.1.20 2 / 2
11.1.19 2 / 2

v11.1.24

1 finding
LOW No provenance attestation provenance

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

v11.1.23

1 finding
LOW No provenance attestation provenance

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

v11.1.22

1 finding
LOW No provenance attestation provenance

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

v11.1.21

1 finding
LOW No provenance attestation provenance

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

v11.1.20

1 finding
LOW No provenance attestation provenance

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

v11.1.19

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.