@mostajs/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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @mostajs/orm is a legitimate multi-dialect ORM package; 'orm' and 'cors' are unrelated acronyms with no brand confusion or impersonation intent. | ai |
Versions (showing 78 of 78)
| Version | Deps | Published |
|---|---|---|
| 2.5.3 | 3 / 7 | |
| 2.5.2 | 3 / 7 | |
| 2.5.1 | 3 / 7 | |
| 2.5.0 | 3 / 7 | |
| 2.2.8 | 3 / 7 | |
| 2.2.7 | 3 / 7 | |
| 2.2.5 | 3 / 7 | |
| 2.2.4 | 3 / 7 | |
| 2.2.3 | 3 / 7 | |
| 2.2.2 | 3 / 7 | |
| 2.2.1 | 3 / 7 | |
| 2.2.0 | 3 / 7 | |
| 2.1.0 | 3 / 7 | |
| 2.0.10 | 0 / 6 | |
| 2.0.0 | 3 / 7 | |
| 1.17.0 | 3 / 7 | |
| 1.16.0 | 3 / 7 | |
| 1.15.0 | 3 / 7 | |
| 1.14.0 | 2 / 7 | |
| 1.13.1 | 1 / 7 | |
| 1.13.0 | 1 / 7 | |
| 1.12.2 | 0 / 7 | |
| 1.12.1 | 0 / 7 | |
| 1.12.0 | 0 / 7 | |
| 1.11.1 | 0 / 7 | |
| 1.11.0 | 0 / 7 | |
| 1.10.8 | 0 / 7 | |
| 1.10.7 | 0 / 7 | |
| 1.10.6 | 0 / 7 | |
| 1.10.0 | 0 / 7 | |
| 1.9.5 | 0 / 7 | |
| 1.9.4 | 0 / 7 | |
| 1.9.3 | 0 / 7 | |
| 1.9.2 | 0 / 7 | |
| 1.9.1 | 0 / 7 | |
| 1.9.0 | 0 / 6 | |
| 1.8.0 | 0 / 6 | |
| 1.7.13 | 0 / 6 | |
| 1.7.12 | 0 / 6 | |
| 1.7.11 | 0 / 6 | |
| 1.7.10 | 0 / 6 | |
| 1.7.9 | 0 / 6 | |
| 1.7.8 | 0 / 6 | |
| 1.7.7 | 0 / 6 | |
| 1.7.6 | 0 / 6 | |
| 1.7.5 | 0 / 6 | |
| 1.7.4 | 0 / 6 | |
| 1.7.3 | 0 / 6 | |
| 1.7.2 | 0 / 6 | |
| 1.7.1 | 0 / 6 | |
| 1.7.0 | 0 / 6 | |
| 1.6.3 | 0 / 6 | |
| 1.6.2 | 0 / 6 | |
| 1.6.1 | 0 / 6 | |
| 1.6.0 | 0 / 6 | |
| 1.5.0 | 0 / 6 | |
| 1.4.17 | 0 / 6 | |
| 1.4.15 | 0 / 6 | |
| 1.4.14 | 0 / 6 | |
| 1.4.13 | 0 / 6 | |
| 1.4.12 | 0 / 6 | |
| 1.4.11 | 0 / 5 | |
| 1.4.10 | 0 / 5 | |
| 1.4.9 | 0 / 5 | |
| 1.4.8 | 0 / 5 | |
| 1.4.7 | 0 / 5 | |
| 1.4.6 | 0 / 5 | |
| 1.4.5 | 0 / 5 | |
| 1.4.4 | 0 / 5 | |
| 1.4.3 | 0 / 5 | |
| 1.4.2 | 0 / 5 | |
| 1.4.1 | 0 / 5 | |
| 1.4.0 | 0 / 5 | |
| 1.3.1 | 0 / 5 | |
| 1.3.0 | 0 / 5 | |
| 1.2.0 | 0 / 5 | |
| 1.1.0 | 0 / 5 | |
| 1.0.0 | 0 / 5 |
v2.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.