@nestjs/core
1
Versions
—
License
Yes
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.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall runs 'opencollective || exit 0' — a standard, benign funding prompt used by many OSS packages. Stable pattern for @nestjs/core across all versions. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @nestjs/core is the legitimate NestJS framework core package, not a typosquat of 'cors'. Scoped namespace and 3268-day history confirm authenticity. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in loadAdapter is intentional NestJS design for optional platform adapter loading (Express/Fastify). Not a security risk in this context. | ai | |
| phantom-deps | phantom-dep:@nuxt/opencollective | AI (phantom-deps): @nuxt/opencollective is invoked by the postinstall script, not imported in source. Expected usage pattern for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): NestJS is a major OSS framework; promotional/sponsor content in README and missing keywords are expected for this project, not spam indicators. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 11.1.19 | 6 / 1 |
v11.1.19
3 findings
HIGH
Package has 'postinstall' script
install-scripts
Script: opencollective || exit 0
HIGH
typosquat.levenshtein: Possible typosquat of 'cors'
typosquat
Package name '@nestjs/core' is 1 edit(s) away from popular package 'cors'.
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.