@comunica/actor-query-result-serialize-stats
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:asynciterator | AI (dependencies): Core dependency of the Comunica ecosystem; stable across all versions. | ai | |
| dependencies | unvetted-dep:@comunica/core | AI (dependencies): Internal monorepo sibling dep; expected for every Comunica package release. | ai | |
| dependencies | unvetted-dep:@comunica/types | AI (dependencies): Internal monorepo sibling dep; expected for every Comunica package release. | ai | |
| dependencies | unvetted-dep:@comunica/bus-http | AI (dependencies): Internal monorepo sibling dep; expected for every Comunica package release. | ai | |
| dependencies | unvetted-dep:@comunica/context-entries | AI (dependencies): Internal monorepo sibling dep; expected for every Comunica package release. | ai | |
| dependencies | unvetted-dep:@comunica/bus-http-invalidate | AI (dependencies): Internal monorepo sibling dep; expected for every Comunica package release. | ai | |
| dependencies | unvetted-dep:@comunica/bus-query-result-serialize | AI (dependencies): Internal monorepo sibling dep; expected for every Comunica package release. | ai | |
| provenance | no-provenance | AI (provenance): Comunica monorepo does not use Sigstore provenance; consistent across all versions. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 5.2.3 | 8 / 0 | |
| 5.2.2 | 8 / 0 | |
| 5.2.0 | 8 / 0 | |
| 5.1.3 | 8 / 0 | |
| 5.1.0 | 8 / 0 | |
| 5.0.3 | 8 / 0 | |
| 5.0.2 | 8 / 0 | |
| 5.0.0 | 8 / 0 | |
| 4.5.0 | 8 / 0 |
v5.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.