@embeddable.com/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
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 org package @embeddable.com/core; not a typosquat of cors — name similarity is coincidental. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 2.13.7 | 1 / 2 | |
| 2.13.6 | 1 / 2 | |
| 2.13.5 | 1 / 2 | |
| 2.13.4 | 2 / 1 | |
| 2.13.3 | 2 / 1 | |
| 2.13.2 | 2 / 1 | |
| 2.13.1 | 2 / 1 | |
| 2.13.0 | 2 / 1 | |
| 2.12.0 | 2 / 1 | |
| 2.11.1 | 2 / 1 | |
| 2.11.0 | 2 / 1 | |
| 2.10.7 | 2 / 1 | |
| 2.10.6 | 2 / 1 | |
| 2.10.5 | 2 / 1 | |
| 2.10.4 | 2 / 1 | |
| 2.10.3 | 2 / 1 | |
| 2.10.2 | 2 / 1 |
v2.13.7
2 findingsPackage name '@embeddable.com/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.
v2.13.6
2 findingsPackage name '@embeddable.com/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.
v2.13.5
2 findingsPackage name '@embeddable.com/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.
v2.13.4
2 findingsPackage name '@embeddable.com/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.
v2.13.3
2 findingsPackage name '@embeddable.com/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.
v2.13.2
2 findingsPackage name '@embeddable.com/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.
v2.13.1
2 findingsPackage name '@embeddable.com/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.
v2.13.0
2 findingsPackage name '@embeddable.com/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.
v2.12.0
2 findingsPackage name '@embeddable.com/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.
v2.11.1
2 findingsPackage name '@embeddable.com/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.
v2.11.0
2 findingsPackage name '@embeddable.com/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.
v2.10.7
2 findingsPackage name '@embeddable.com/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.
v2.10.6
2 findingsPackage name '@embeddable.com/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.
v2.10.5
2 findingsPackage name '@embeddable.com/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.
v2.10.4
2 findingsPackage name '@embeddable.com/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.
v2.10.3
2 findingsPackage name '@embeddable.com/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.
v2.10.2
2 findingsPackage name '@embeddable.com/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.