@the-situation/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; name similarity to 'cors' is coincidental, not impersonation. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.12.0 | 1 / 2 | |
| 0.11.1 | 1 / 2 | |
| 0.11.0 | 1 / 2 | |
| 0.9.6 | 1 / 2 | |
| 0.9.5 | 1 / 2 | |
| 0.9.4 | 1 / 2 | |
| 0.9.3 | 1 / 2 | |
| 0.9.1 | 1 / 2 | |
| 0.8.13 | 1 / 2 | |
| 0.8.12 | 1 / 2 | |
| 0.8.11 | 1 / 2 | |
| 0.8.10 | 1 / 2 | |
| 0.8.9 | 1 / 2 | |
| 0.8.8 | 1 / 2 | |
| 0.8.6 | 1 / 2 | |
| 0.8.5 | 1 / 2 | |
| 0.8.4 | 1 / 2 | |
| 0.8.0 | 1 / 2 |
v0.12.0
2 findingsPackage name '@the-situation/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.1
2 findingsPackage name '@the-situation/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 '@the-situation/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.9.6
2 findingsPackage name '@the-situation/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.9.5
2 findingsPackage name '@the-situation/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.9.4
2 findingsPackage name '@the-situation/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.9.3
2 findingsPackage name '@the-situation/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.9.1
2 findingsPackage name '@the-situation/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.8.13
2 findingsPackage name '@the-situation/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.8.12
2 findingsPackage name '@the-situation/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.8.11
2 findingsPackage name '@the-situation/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.8.10
2 findingsPackage name '@the-situation/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.8.9
2 findingsPackage name '@the-situation/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.8.8
2 findingsPackage name '@the-situation/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.8.6
2 findingsPackage name '@the-situation/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.8.5
2 findingsPackage name '@the-situation/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.8.4
2 findingsPackage name '@the-situation/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.8.0
2 findingsPackage name '@the-situation/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.