SPARQL console A standard SPARQL 1.1 endpoint at /sparql, answered by Oxigraph directly — nothing in this app inspects or rewrites your query. The store is opened read-only, so updates are refused by the server that would have to perform them. Point any client at it, not just this page.
What is in here?
Triple counts per named graph.
The split is deliberate: vocabulary, registry facts, per-run metrics and provenance are separate graphs.
Official modules
Every module maintained by the Nuxt core team, with its category.
Most downloaded
Latest download count per npm package.
Counts are timestamped observations, not properties. The FILTER NOT EXISTS is what selects the newest one — drop it and you get every run ever recorded.
Still requires Nuxt Bridge
Modules whose compatibility statement names a Bridge requirement.
Who works on the most modules
People ranked by number of modules they have committed to, with total commits.
Contributions are reified so each carries a commit count. schema:contributor is also asserted for the simpler question.
Listed maintainers with no recorded commits
Maintainers with no recorded contribution to the module they maintain.
The kind of question a graph answers directly and a REST API does not.
Modules with no contributor data
Modules the feed supplied no contributor list for at all.
A missing metric is recorded as a gap; a missing contributor list is not recorded anywhere, so MINUS over the reified contributions is the only way to see it. These are the modules where "never committed" cannot be asked — which is why the query above restricts itself to modules whose commits were collected.
What the source feed did not supply
Metric gaps recorded per pipeline run.
The feed reports uncollected counts as 0. Those are dropped rather than asserted, and the gap is recorded here instead — so "no data" stays distinguishable from "zero".
Category distribution by module type
Cross-tabulation of category against official/community/third-party.