@stytch/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 package under legitimate @stytch org; name similarity to 'cors' is coincidental, not a squatting attempt. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 2.66.1 | 1 / 19 | |
| 2.66.0 | 1 / 19 | |
| 2.65.0 | 1 / 19 | |
| 2.64.1 | 1 / 19 | |
| 2.64.0 | 1 / 19 | |
| 2.63.0 | 1 / 19 | |
| 2.62.1 | 1 / 19 | |
| 2.62.0 | 1 / 19 | |
| 2.61.1 | 1 / 19 | |
| 2.61.0 | 1 / 19 | |
| 2.60.0 | 1 / 19 | |
| 2.59.0 | 1 / 19 | |
| 2.58.1 | 1 / 19 | |
| 2.58.0 | 1 / 19 | |
| 2.57.0 | 1 / 19 | |
| 2.56.0 | 1 / 19 | |
| 2.55.0 | 1 / 19 | |
| 2.54.0 | 1 / 19 | |
| 2.53.0 | 1 / 19 | |
| 2.52.1 | 1 / 19 | |
| 2.52.0 | 1 / 19 | |
| 2.51.2 | 1 / 19 | |
| 2.51.1 | 1 / 19 | |
| 2.51.0 | 1 / 19 | |
| 2.50.2 | 1 / 19 | |
| 2.50.1 | 1 / 19 | |
| 2.50.0 | 1 / 19 | |
| 2.49.1 | 1 / 19 |
v2.66.1
2 findingsPackage name '@stytch/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.66.0
2 findingsPackage name '@stytch/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.65.0
2 findingsPackage name '@stytch/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.64.1
2 findingsPackage name '@stytch/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.64.0
2 findingsPackage name '@stytch/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.63.0
2 findingsPackage name '@stytch/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.62.1
2 findingsPackage name '@stytch/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.62.0
2 findingsPackage name '@stytch/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.61.1
2 findingsPackage name '@stytch/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.61.0
2 findingsPackage name '@stytch/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.60.0
2 findingsPackage name '@stytch/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.59.0
2 findingsPackage name '@stytch/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.58.1
2 findingsPackage name '@stytch/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.58.0
2 findingsPackage name '@stytch/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.57.0
2 findingsPackage name '@stytch/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.56.0
2 findingsPackage name '@stytch/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.55.0
2 findingsPackage name '@stytch/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.54.0
2 findingsPackage name '@stytch/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.53.0
2 findingsPackage name '@stytch/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.52.1
2 findingsPackage name '@stytch/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.52.0
2 findingsPackage name '@stytch/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.51.2
2 findingsPackage name '@stytch/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.51.1
2 findingsPackage name '@stytch/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.51.0
2 findingsPackage name '@stytch/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.50.2
2 findingsPackage name '@stytch/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.50.1
2 findingsPackage name '@stytch/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.50.0
2 findingsPackage name '@stytch/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.49.1
2 findingsPackage name '@stytch/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.