@rschedule/core
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
jcarroll
Keywords
rschedulejavascripttypescript
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @rschedule/core is a legitimate scoped scheduling library; 'core' is a common sub-package name with no intent to impersonate the unscoped 'cors' package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): This is a sub-path entry point package in a monorepo; short README and no deps are expected for this pattern. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.5.0 | 0 / 0 |
v1.5.0
2 findings
HIGH
typosquat.levenshtein: Possible typosquat of 'cors'
typosquat
Package name '@rschedule/core' is 1 edit(s) away from popular package 'cors'.
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.