@loopback/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): @loopback/core is the canonical LoopBack framework core package by IBM; not a typosquat of cors. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 7.0.12 | 3 / 5 | |
| 7.0.11 | 3 / 5 | |
| 7.0.10 | 3 / 5 | |
| 7.0.9 | 3 / 5 | |
| 7.0.8 | 3 / 5 | |
| 7.0.7 | 3 / 5 | |
| 7.0.6 | 3 / 5 | |
| 7.0.5 | 3 / 5 | |
| 7.0.4 | 3 / 5 | |
| 7.0.3 | 3 / 5 | |
| 7.0.2 | 3 / 5 | |
| 7.0.1 | 3 / 5 | |
| 7.0.0 | 3 / 5 |
v7.0.12
2 findingsPackage name '@loopback/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.
v7.0.11
2 findingsPackage name '@loopback/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.
v7.0.10
2 findingsPackage name '@loopback/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.
v7.0.9
2 findingsPackage name '@loopback/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.
v7.0.8
2 findingsPackage name '@loopback/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.
v7.0.7
2 findingsPackage name '@loopback/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.
v7.0.6
2 findingsPackage name '@loopback/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.
v7.0.5
2 findingsPackage name '@loopback/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.
v7.0.4
2 findingsPackage name '@loopback/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.
v7.0.3
2 findingsPackage name '@loopback/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.
v7.0.2
2 findingsPackage name '@loopback/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.
v7.0.1
2 findingsPackage name '@loopback/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.
v7.0.0
2 findingsPackage name '@loopback/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.