@nestjs/mercurius
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
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 13.4.2 | 1 / 8 | |
| 13.4.0 | 1 / 8 | |
| 13.3.0 | 1 / 8 | |
| 13.2.5 | 1 / 8 | |
| 13.2.4 | 1 / 8 | |
| 13.2.3 | 1 / 8 | |
| 13.2.0 | 1 / 8 | |
| 13.1.0 | 1 / 8 | |
| 13.0.4 | 1 / 8 | |
| 13.0.3 | 1 / 8 | |
| 13.0.2 | 1 / 8 | |
| 13.0.1 | 1 / 8 | |
| 13.0.0 | 1 / 8 |
v13.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.