← Home

@nestjs/cli

npm Repository Homepage
23
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

nestjscorekamilmysliwiec

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:dynamic-require AI (semgrep): Loads user-specified webpack config files; documented CLI behavior, not arbitrary code execution. ai
semgrep semgrep:child-process-import AI (semgrep): Used for scaffolding new NestJS projects; core CLI functionality, not malicious. ai
typosquat typosquat.levenshtein:joi AI (typosquat): @nestjs/cli is a well-known scoped package; levenshtein match to 'joi' is a false positive. ai
phantom-deps phantom-dep:@nestjs/schematics AI (phantom-deps): Same-org dependency used transitively via schematics; stable false positive for this package. ai
phantom-deps phantom-dep:@angular-devkit/core AI (phantom-deps): Referenced in config files as documented; stable false positive for this CLI package. ai

Versions (showing 23 of 23)

Version Deps Published
11.0.23 18 / 24
11.0.22 18 / 24
11.0.21 18 / 24
11.0.20 18 / 24
11.0.19 18 / 24
11.0.18 18 / 24
11.0.17 18 / 24
11.0.16 18 / 24
11.0.15 18 / 24
11.0.14 18 / 24
11.0.12 18 / 24
11.0.11 18 / 24
11.0.10 19 / 24
11.0.9 19 / 24
11.0.8 19 / 24
11.0.7 19 / 24
11.0.6 19 / 24
11.0.5 19 / 24
11.0.4 19 / 24
11.0.3 19 / 24
11.0.2 19 / 24
11.0.1 19 / 24
11.0.0 19 / 24

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

1 finding
LOW No provenance attestation provenance

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

v11.0.16

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

1 finding
LOW No provenance attestation provenance

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

v11.0.6

1 finding
LOW No provenance attestation provenance

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

v11.0.4

1 finding
LOW No provenance attestation provenance

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

v11.0.3

1 finding
LOW No provenance attestation provenance

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

v11.0.2

1 finding
LOW No provenance attestation provenance

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

v11.0.1

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

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.