@rivetkit/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 |
|---|---|---|---|---|
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get used in a Proxy handler for method binding — standard JS pattern, not obfuscation. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): 127.0.0.1 in driver test suite is a localhost test endpoint, not exfiltration. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @rivetkit/core is part of the rivetkit ecosystem, not a typosquat of cors. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Intentional placeholder stub; sparse metadata is expected for this package type. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 2.0.23 | 0 / 3 | |
| 2.0.22 | 0 / 3 | |
| 2.0.21 | 0 / 3 | |
| 2.0.20 | 0 / 3 | |
| 2.0.19 | 0 / 3 | |
| 2.0.18 | 0 / 3 | |
| 2.0.17 | 0 / 3 | |
| 2.0.16 | 0 / 3 | |
| 2.0.15 | 0 / 3 | |
| 2.0.14 | 0 / 3 | |
| 2.0.13 | 0 / 3 | |
| 2.0.12 | 0 / 3 | |
| 2.0.11 | 0 / 3 | |
| 2.0.10 | 0 / 3 | |
| 2.0.9 | 0 / 3 | |
| 2.0.8 | 0 / 3 | |
| 2.0.7 | 0 / 3 | |
| 2.0.6 | 0 / 3 | |
| 2.0.5 | 0 / 3 | |
| 2.0.4 | 0 / 3 | |
| 2.0.3 | 0 / 3 |
v2.0.23
2 findingsPackage name '@rivetkit/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.0.22
2 findingsPackage name '@rivetkit/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.0.21
2 findingsPackage name '@rivetkit/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.0.20
2 findingsPackage name '@rivetkit/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.0.19
2 findingsPackage name '@rivetkit/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.0.18
2 findingsPackage name '@rivetkit/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.0.17
2 findingsPackage name '@rivetkit/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.0.16
2 findingsPackage name '@rivetkit/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.0.15
2 findingsPackage name '@rivetkit/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.0.14
2 findingsPackage name '@rivetkit/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.0.13
2 findingsPackage name '@rivetkit/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.0.12
2 findingsPackage name '@rivetkit/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.0.11
2 findingsPackage name '@rivetkit/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.0.10
2 findingsPackage name '@rivetkit/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.0.9
2 findingsPackage name '@rivetkit/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.0.8
2 findingsPackage name '@rivetkit/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.0.7
2 findingsPackage name '@rivetkit/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.0.6
2 findingsPackage name '@rivetkit/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.0.5
2 findingsPackage name '@rivetkit/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.0.4
2 findingsPackage name '@rivetkit/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.0.3
2 findingsPackage name '@rivetkit/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.