@yumerijs/core
Core module for yumeri
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 @yumerijs/core is a framework core module, not a typosquat of cors; name similarity is coincidental. | ai | |
| phantom-deps | phantom-dep:js-yaml | AI (phantom-deps): js-yaml is a legitimate runtime dep used in config handling; heuristic false positive. | ai | |
| phantom-deps | phantom-dep:chokidar | AI (phantom-deps): chokidar is a legitimate runtime dep for file watching; heuristic false positive. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 2.2.2 | 6 / 6 | |
| 2.2.1 | 6 / 6 | |
| 2.2.0 | 6 / 6 | |
| 2.1.1 | 6 / 6 | |
| 2.1.0 | 6 / 6 | |
| 2.0.14 | 6 / 6 | |
| 2.0.13 | 6 / 6 | |
| 2.0.12 | 6 / 6 | |
| 2.0.11 | 6 / 6 | |
| 2.0.10 | 6 / 6 | |
| 2.0.9 | 6 / 6 | |
| 2.0.8 | 6 / 6 | |
| 2.0.7 | 6 / 6 | |
| 2.0.6 | 6 / 6 | |
| 2.0.5 | 6 / 6 | |
| 2.0.4 | 6 / 6 |
v2.2.2
2 findingsPackage name '@yumerijs/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.2.1
2 findingsPackage name '@yumerijs/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.2.0
2 findingsPackage name '@yumerijs/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.1.1
2 findingsPackage name '@yumerijs/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.1.0
2 findingsPackage name '@yumerijs/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 '@yumerijs/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 '@yumerijs/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 '@yumerijs/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 '@yumerijs/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 '@yumerijs/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 '@yumerijs/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 '@yumerijs/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 '@yumerijs/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 '@yumerijs/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 '@yumerijs/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 '@yumerijs/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.