@faber-js/orm
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Package has no CI provenance setup; consistent across versions, not a security risk on its own. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @faber-js/orm is an ORM package; Levenshtein match to 'cors' is coincidental, not a squatting attempt. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.4.0 | 3 / 3 | |
| 1.3.0 | 3 / 3 | |
| 1.2.2 | 3 / 3 | |
| 1.1.9 | 3 / 3 | |
| 1.1.8 | 3 / 3 | |
| 1.1.6 | 3 / 3 | |
| 1.1.4 | 3 / 3 | |
| 1.0.26 | 3 / 2 | |
| 1.0.24 | 3 / 2 | |
| 1.0.22 | 3 / 2 | |
| 1.0.19 | 3 / 2 | |
| 1.0.7 | 3 / 2 | |
| 1.0.4 | 3 / 2 | |
| 1.0.3 | 3 / 2 | |
| 1.0.2 | 3 / 2 | |
| 1.0.1 | 3 / 2 | |
| 1.0.0 | 3 / 2 |
v1.4.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: echovick.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: echovick.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.