@contract-kit/next
Next.js server-side handlers 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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@contract-kit/domain | AI (phantom-deps): Same-org monorepo dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:@contract-kit/application | AI (phantom-deps): Same-org monorepo dep; stable false positive. | ai | |
| typosquat | typosquat.levenshtein:nuxt | AI (typosquat): @contract-kit/next is a Next.js adapter in a monorepo, not a typosquat of nuxt. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): 2-edit distance false positive; package is clearly a Next.js integration utility. | ai | |
| typosquat | typosquat.levenshtein:knex | AI (typosquat): 2-edit distance false positive; unrelated to knex. | ai | |
| phantom-deps | phantom-dep:@contract-kit/core | AI (phantom-deps): Same-org monorepo dep; may be re-exported transitively rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@contract-kit/errors | AI (phantom-deps): Same-org monorepo dep; transitive re-export pattern is expected. | ai | |
| phantom-deps | phantom-dep:@standard-schema/spec | AI (phantom-deps): Referenced in config/type files; stable false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.1.10 | 6 / 6 | |
| 0.1.9 | 6 / 6 | |
| 0.1.8 | 6 / 6 | |
| 0.1.7 | 5 / 6 | |
| 0.1.6 | 5 / 6 | |
| 0.1.5 | 5 / 6 | |
| 0.1.4 | 5 / 6 | |
| 0.1.2 | 7 / 6 | |
| 0.1.1 | 7 / 6 | |
| 0.0.1 | 4 / 5 |
v0.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
2 findingsPackage name '@contract-kit/next' is 1 edit(s) away from popular package 'nuxt'.
Package 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. Consider requesting the maintainer enable provenance via CI/CD.
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.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
2 findingsPackage name '@contract-kit/next' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
2 findingsPackage name '@contract-kit/next' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.