@gluhar/sanity
Gluhar Sanity package. Configures @nuxtjs/sanity under the hood. Provides composables, etc. Depends on @gluhar/i18n for localization of fields.
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:@gluhar/core | AI (dependencies): Same @gluhar publisher namespace; internal dependency consistent across versions. | ai | |
| phantom-deps | phantom-dep:@gluhar/core | AI (phantom-deps): Same-org dep loaded by Nuxt module convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@gluhar/i18n | AI (phantom-deps): Same-org dep loaded by Nuxt module convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:defu | AI (phantom-deps): Used in config files by convention in Nuxt modules; stable false positive. | ai | |
| phantom-deps | phantom-dep:@nuxt/kit | AI (phantom-deps): Framework-scoped package loaded by Nuxt convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:@nuxtjs/sanity | AI (phantom-deps): Referenced in config files per Nuxt module pattern; stable false positive. | ai | |
| provenance | no-provenance | AI (provenance): Scoped private-org package; no provenance is consistent across all versions in this ecosystem. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 5.2.0 | 5 / 10 | |
| 5.1.5 | 5 / 10 | |
| 5.0.4 | 5 / 10 | |
| 5.0.3 | 5 / 10 | |
| 5.0.2 | 5 / 10 | |
| 5.0.1 | 5 / 10 | |
| 5.0.0 | 5 / 10 |
v5.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.4
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.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.