← Home

@comunica/actor-query-operation-group

9
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

joachimvhrubensworksrubenverborghdexagodjeswr

Keywords

comunicaactorquery-operationgroup

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:sparqlalgebrajs AI (dependencies): sparqlalgebrajs is a core SPARQL algebra library integral to Comunica's query stack; stable dependency for this package. ai
dependencies unvetted-dep:asynciterator AI (dependencies): asynciterator is a well-known streaming library used throughout Comunica. ai
dependencies unvetted-dep:@comunica/core AI (dependencies): Sibling monorepo package; stable dependency pattern across all Comunica actors. ai
dependencies unvetted-dep:@comunica/types AI (dependencies): Sibling monorepo package; stable dependency pattern. ai
dependencies unvetted-dep:@comunica/utils-algebra AI (dependencies): Sibling monorepo package; stable dependency pattern. ai
dependencies unvetted-dep:@comunica/context-entries AI (dependencies): Sibling monorepo package; stable dependency pattern. ai
provenance no-provenance AI (provenance): Established Comunica monorepo; provenance not used across the ecosystem. ai
dependencies unvetted-dep:@comunica/utils-query-operation AI (dependencies): Sibling monorepo package; stable dependency pattern. ai
dependencies unvetted-dep:@comunica/utils-bindings-factory AI (dependencies): Sibling monorepo package; stable dependency pattern. ai
dependencies unvetted-dep:@comunica/bus-merge-bindings-context AI (dependencies): Sibling monorepo package; stable dependency pattern. ai
dependencies unvetted-dep:@comunica/bus-bindings-aggregator-factory AI (dependencies): Sibling monorepo package; stable dependency pattern. ai
dependencies unvetted-dep:@comunica/bus-query-operation AI (dependencies): Sibling monorepo package; stable dependency pattern. ai

Versions (showing 9 of 9)

Version Deps Published
5.2.3 11 / 0
5.2.2 11 / 0
5.2.0 11 / 0
5.1.3 11 / 0
5.1.0 11 / 0
5.0.3 11 / 0
5.0.2 11 / 0
5.0.0 11 / 0
4.5.0 11 / 0

v5.2.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.2.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v5.1.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.1.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v4.5.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.