@nestjs/platform-express
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Official NestJS framework package; README signals are false positives for a large documentation-rich monorepo package. | ai |
Versions (showing 51 of 53)
| Version | Deps | Published |
|---|---|---|
| 11.1.28 | 5 / 2 | |
| 11.1.27 | 5 / 2 | |
| 11.1.26 | 5 / 2 | |
| 11.1.25 | 5 / 2 | |
| 11.1.24 | 5 / 2 | |
| 11.1.23 | 5 / 2 | |
| 11.1.22 | 5 / 2 | |
| 11.1.21 | 5 / 2 | |
| 11.1.20 | 5 / 2 | |
| 11.1.19 | 5 / 2 | |
| 11.1.18 | 5 / 2 | |
| 11.1.17 | 5 / 2 | |
| 11.1.16 | 5 / 2 | |
| 11.1.15 | 5 / 2 | |
| 11.1.14 | 5 / 2 | |
| 11.1.13 | 5 / 2 | |
| 11.1.12 | 5 / 2 | |
| 11.1.11 | 5 / 2 | |
| 11.1.10 | 5 / 2 | |
| 11.1.9 | 5 / 2 | |
| 11.1.8 | 5 / 2 | |
| 11.1.7 | 5 / 2 | |
| 11.1.6 | 5 / 2 | |
| 11.1.5 | 5 / 2 | |
| 11.1.4 | 5 / 2 | |
| 11.1.3 | 5 / 2 | |
| 11.1.2 | 5 / 2 | |
| 11.1.1 | 5 / 2 | |
| 11.1.0 | 5 / 2 | |
| 11.0.21 | 5 / 2 | |
| 11.0.20 | 5 / 2 | |
| 11.0.19 | 5 / 2 | |
| 11.0.18 | 5 / 2 | |
| 11.0.17 | 5 / 2 | |
| 11.0.16 | 5 / 2 | |
| 11.0.15 | 5 / 2 | |
| 11.0.14 | 5 / 2 | |
| 11.0.13 | 5 / 2 | |
| 11.0.12 | 5 / 2 | |
| 11.0.11 | 5 / 2 | |
| 11.0.10 | 5 / 2 | |
| 11.0.9 | 5 / 2 | |
| 11.0.8 | 5 / 2 | |
| 11.0.7 | 5 / 2 | |
| 11.0.6 | 5 / 2 | |
| 11.0.5 | 5 / 2 | |
| 11.0.4 | 5 / 2 | |
| 11.0.3 | 5 / 2 | |
| 11.0.2 | 4 / 2 | |
| 11.0.1 | 5 / 2 | |
| 11.0.0 | 5 / 2 |
v11.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.