@gscdump/nuxt-analytics
Nuxt layer: GSC analytics UI + DuckDB-WASM integration. Frontend-only; server primitives live in @gscdump/analysis, @gscdump/engine-sqlite, @gscdump/cloudflare, and host apps.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@unovis/ts | AI (dependencies): @unovis/ts is a legitimate open-source data visualization library; stable dependency for this Nuxt analytics package. | ai | |
| dependencies | unvetted-dep:@unovis/vue | AI (dependencies): @unovis/vue is the Vue wrapper for the same legitimate @unovis visualization library. | ai | |
| provenance | no-provenance | AI (provenance): Published via GitHub Actions CI; provenance attestation not yet configured but no other risk signals present. | ai | |
| phantom-deps | phantom-dep:@unovis/vue | AI (phantom-deps): Referenced in config files as expected for a Nuxt layer visualization dep. | ai | |
| phantom-deps | phantom-dep:tailwindcss | AI (phantom-deps): Nuxt layer config-level dep; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@vueuse/core | AI (phantom-deps): Nuxt layer convention; loaded by framework. | ai | |
| phantom-deps | phantom-dep:@vueuse/nuxt | AI (phantom-deps): Nuxt layer convention; loaded by framework. | ai | |
| phantom-deps | phantom-dep:@duckdb/duckdb-wasm | AI (phantom-deps): Platform-specific WASM binary; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@unovis/ts | AI (phantom-deps): Referenced in config files as expected for a Nuxt layer visualization dep. | ai | |
| phantom-deps | phantom-dep:@nuxt/ui | AI (phantom-deps): Nuxt layer convention; loaded by framework, not directly imported. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 0.18.6 | 15 / 4 | |
| 0.18.5 | 15 / 4 | |
| 0.18.4 | 15 / 4 | |
| 0.18.3 | 15 / 4 | |
| 0.18.2 | 15 / 4 | |
| 0.18.1 | 15 / 4 | |
| 0.18.0 | 15 / 4 | |
| 0.17.5 | 15 / 4 | |
| 0.17.4 | 15 / 4 | |
| 0.17.3 | 15 / 4 | |
| 0.17.2 | 15 / 4 | |
| 0.17.1 | 15 / 4 | |
| 0.17.0 | 15 / 4 | |
| 0.13.1 | 15 / 4 | |
| 0.13.0 | 15 / 4 | |
| 0.12.0 | 15 / 4 | |
| 0.11.5 | 15 / 4 | |
| 0.11.4 | 13 / 4 | |
| 0.11.3 | 13 / 4 | |
| 0.11.2 | 13 / 3 | |
| 0.11.1 | 13 / 3 | |
| 0.11.0 | 13 / 3 | |
| 0.10.0 | 13 / 3 | |
| 0.9.2 | 12 / 3 | |
| 0.9.1 | 12 / 3 | |
| 0.9.0 | 12 / 3 | |
| 0.8.2 | 12 / 3 | |
| 0.8.1 | 12 / 3 | |
| 0.8.0 | 12 / 3 | |
| 0.7.6 | 12 / 3 | |
| 0.7.5 | 12 / 3 | |
| 0.7.1 | 11 / 3 | |
| 0.6.3 | 15 / 4 | |
| 0.6.2 | 15 / 4 | |
| 0.4.0 | 15 / 4 |
v0.18.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.