@contract-kit/nuqs
nuqs integration for contract-kit
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:nuxt | AI (typosquat): Package is a nuqs integration in the @contract-kit monorepo; name is intentional, not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Same rationale — scoped monorepo package named after nuqs library it wraps. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.1.10 | 3 / 7 | |
| 0.1.9 | 3 / 7 | |
| 0.1.8 | 3 / 7 | |
| 0.1.7 | 3 / 7 | |
| 0.1.6 | 3 / 7 | |
| 0.1.5 | 3 / 7 |
v0.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.