@graphql-yoga/nestjs
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): theguild-bot is the org's trusted CI publisher with strong track record and SLSA attestation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same org CI bot transition, not a suspicious takeover. | ai |
Versions (showing 56 of 56)
| Version | Deps | Published |
|---|---|---|
| 3.22.2 | 0 / 23 | |
| 3.22.1 | 0 / 23 | |
| 3.22.0 | 0 / 23 | |
| 3.21.0 | 0 / 23 | |
| 3.20.0 | 0 / 23 | |
| 3.19.1 | 0 / 23 | |
| 3.19.0 | 0 / 23 | |
| 3.18.1 | 0 / 23 | |
| 3.18.0 | 0 / 23 | |
| 3.17.1 | 0 / 23 | |
| 3.17.0 | 0 / 23 | |
| 3.16.0 | 0 / 23 | |
| 3.15.2 | 0 / 23 | |
| 3.15.1 | 0 / 24 | |
| 3.15.0 | 0 / 24 | |
| 3.14.0 | 0 / 24 | |
| 3.13.5 | 0 / 24 | |
| 3.13.4 | 0 / 24 | |
| 3.13.3 | 0 / 24 | |
| 3.13.2 | 0 / 24 | |
| 3.13.1 | 0 / 24 | |
| 3.13.0 | 0 / 24 | |
| 3.12.2 | 0 / 24 | |
| 3.12.1 | 0 / 24 | |
| 3.12.0 | 0 / 24 | |
| 3.11.0 | 0 / 24 | |
| 3.10.12 | 0 / 24 | |
| 3.10.11 | 0 / 24 | |
| 3.10.10 | 0 / 24 | |
| 3.10.9 | 0 / 24 | |
| 3.10.8 | 0 / 24 | |
| 3.10.7 | 0 / 24 | |
| 3.10.6 | 0 / 24 | |
| 3.10.5 | 0 / 24 | |
| 3.10.4 | 0 / 24 | |
| 3.10.3 | 0 / 24 | |
| 3.10.2 | 0 / 24 | |
| 3.10.1 | 0 / 24 | |
| 3.10.0 | 0 / 24 | |
| 3.9.0 | 0 / 24 | |
| 3.8.0 | 0 / 24 | |
| 3.7.0 | 0 / 24 | |
| 3.6.3 | 0 / 24 | |
| 3.6.2 | 0 / 24 | |
| 3.6.1 | 0 / 24 | |
| 3.6.0 | 0 / 24 | |
| 3.5.0 | 0 / 24 | |
| 3.4.0 | 0 / 24 | |
| 3.3.1 | 0 / 24 | |
| 3.3.0 | 0 / 24 | |
| 3.2.0 | 0 / 24 | |
| 3.1.1 | 0 / 24 | |
| 3.1.0 | 0 / 24 | |
| 3.0.2 | 0 / 24 | |
| 3.0.1 | 0 / 24 | |
| 3.0.0 | 0 / 24 |
v3.13.4
2 findingsThis version was published by a different npm account than previous versions on 2025-04-15. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.13.3
2 findingsThis version was published by a different npm account than previous versions on 2025-04-09. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.13.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.13.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.12.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.12.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.10.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.10.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.10.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.10.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.10.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.10.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.10.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.10.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.10.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.10.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.10.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.10.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.6.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.6.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.