@yinuo-ngm/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 in a coherent @yinuo-ngm/* monorepo; not an impersonation of cors. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo core package; missing metadata is expected for org-internal tooling. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.1.13 | 17 / 0 | |
| 0.1.12 | 14 / 0 | |
| 0.1.11 | 14 / 0 | |
| 0.1.10 | 12 / 0 | |
| 0.1.9 | 12 / 0 |
v0.1.13
2 findingsPackage name '@yinuo-ngm/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.
v0.1.12
2 findingsPackage name '@yinuo-ngm/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.
v0.1.11
2 findingsPackage name '@yinuo-ngm/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.
v0.1.10
2 findingsPackage name '@yinuo-ngm/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.
v0.1.9
2 findingsPackage name '@yinuo-ngm/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.