@sdk-it/core
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped SDK package @sdk-it/core; name similarity to 'cors' is coincidental, not a typosquat. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 0.43.0 | 4 / 1 | |
| 0.42.1 | 4 / 1 | |
| 0.42.0 | 4 / 1 | |
| 0.41.0 | 4 / 1 | |
| 0.40.0 | 4 / 1 | |
| 0.39.0 | 4 / 1 | |
| 0.38.0 | 4 / 1 | |
| 0.37.1 | 4 / 1 | |
| 0.37.0 | 4 / 1 | |
| 0.36.2 | 4 / 1 | |
| 0.36.1 | 4 / 1 | |
| 0.36.0 | 4 / 1 | |
| 0.35.1 | 4 / 1 | |
| 0.35.0 | 4 / 1 | |
| 0.34.1 | 4 / 1 | |
| 0.34.0 | 4 / 1 | |
| 0.33.3 | 4 / 1 | |
| 0.33.2 | 4 / 1 | |
| 0.33.1 | 4 / 1 | |
| 0.33.0 | 4 / 1 | |
| 0.32.0 | 4 / 1 | |
| 0.31.2 | 4 / 1 | |
| 0.31.1 | 4 / 1 | |
| 0.31.0 | 4 / 1 | |
| 0.30.0 | 4 / 1 | |
| 0.29.0 | 4 / 1 | |
| 0.28.0 | 4 / 1 | |
| 0.27.0 | 4 / 1 | |
| 0.26.0 | 4 / 1 | |
| 0.25.0 | 4 / 1 | |
| 0.24.0 | 4 / 1 | |
| 0.23.0 | 4 / 1 | |
| 0.22.1 | 4 / 1 | |
| 0.22.0 | 4 / 1 | |
| 0.21.0 | 4 / 1 |
v0.43.0
2 findingsPackage name '@sdk-it/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.42.1
2 findingsPackage name '@sdk-it/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.42.0
2 findingsPackage name '@sdk-it/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.41.0
2 findingsPackage name '@sdk-it/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.40.0
2 findingsPackage name '@sdk-it/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.39.0
2 findingsPackage name '@sdk-it/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.38.0
2 findingsPackage name '@sdk-it/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.37.1
2 findingsPackage name '@sdk-it/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.37.0
2 findingsPackage name '@sdk-it/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.36.2
2 findingsPackage name '@sdk-it/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.36.1
2 findingsPackage name '@sdk-it/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.36.0
2 findingsPackage name '@sdk-it/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.35.1
2 findingsPackage name '@sdk-it/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.35.0
2 findingsPackage name '@sdk-it/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.34.1
2 findingsPackage name '@sdk-it/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.34.0
2 findingsPackage name '@sdk-it/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.33.3
2 findingsPackage name '@sdk-it/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.33.2
2 findingsPackage name '@sdk-it/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.33.1
2 findingsPackage name '@sdk-it/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.33.0
2 findingsPackage name '@sdk-it/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.32.0
2 findingsPackage name '@sdk-it/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.31.2
2 findingsPackage name '@sdk-it/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.31.1
2 findingsPackage name '@sdk-it/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.31.0
2 findingsPackage name '@sdk-it/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.30.0
2 findingsPackage name '@sdk-it/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.29.0
2 findingsPackage name '@sdk-it/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.28.0
2 findingsPackage name '@sdk-it/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.27.0
2 findingsPackage name '@sdk-it/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.26.0
2 findingsPackage name '@sdk-it/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.25.0
2 findingsPackage name '@sdk-it/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.24.0
2 findingsPackage name '@sdk-it/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.23.0
2 findingsPackage name '@sdk-it/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.22.1
2 findingsPackage name '@sdk-it/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.22.0
2 findingsPackage name '@sdk-it/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.21.0
2 findingsPackage name '@sdk-it/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.