@contractkit/core
Core DSL compiler library: grammar-driven parser, codegen, and validation
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:cors | AI (typosquat): Scoped package @contractkit/core is a DSL compiler, not a typosquat of cors; name similarity is coincidental. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.20.0 | 1 / 2 | |
| 0.19.0 | 1 / 2 | |
| 0.18.0 | 1 / 2 | |
| 0.17.0 | 1 / 2 | |
| 0.16.0 | 1 / 2 | |
| 0.15.1 | 1 / 2 | |
| 0.15.0 | 1 / 2 | |
| 0.14.0 | 1 / 2 | |
| 0.13.0 | 1 / 2 | |
| 0.12.0 | 1 / 2 | |
| 0.11.0 | 1 / 2 |
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
2 findingsPackage name '@contractkit/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
2 findingsPackage name '@contractkit/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
2 findingsPackage name '@contractkit/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.1
2 findingsPackage name '@contractkit/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
2 findingsPackage name '@contractkit/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
2 findingsPackage name '@contractkit/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
2 findingsPackage name '@contractkit/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
2 findingsPackage name '@contractkit/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
2 findingsPackage name '@contractkit/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.