@rxdi/graphql-nats
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@rxdi/nats | AI (phantom-deps): Dependency is used in library code; false positive for scoped packages. | ai | |
| phantom-deps | phantom-dep:graphql-subscriptions | AI (phantom-deps): Dependency is used in library code; false positive for scoped packages. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.7.248 | 2 / 7 | |
| 0.7.247 | 2 / 7 | |
| 0.7.246 | 2 / 7 | |
| 0.7.245 | 2 / 7 | |
| 0.7.244 | 2 / 7 | |
| 0.7.243 | 2 / 7 | |
| 0.7.242 | 2 / 7 | |
| 0.7.241 | 2 / 7 | |
| 0.7.240 | 2 / 7 |
v0.7.248
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.247
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.246
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.245
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.244
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.243
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.242
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.241
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.240
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.