@mostajs/net
Multi-protocol transport layer for @mostajs/orm — expose entities via REST, gRPC, GraphQL, WebSocket, SSE, tRPC, MCP, OData, Arrow Flight, JSON-RPC, NATS
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:next | AI (typosquat): @mostajs/net is a scoped transport-layer package; 'net' is a natural abbreviation for networking, not an impersonation of 'next'. Levenshtein match is a false positive for this namespace. | ai | |
| typosquat | typosquat.levenshtein:nuxt | AI (typosquat): 2-edit distance from 'nuxt' is coincidental; @mostajs/net is a transport layer for @mostajs/orm, not related to Nuxt. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): 2-edit distance from 'jest' is coincidental; package is a networking/transport layer with no relation to testing frameworks. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): 2-edit distance from 'got' is coincidental; package is a multi-protocol transport layer, not an HTTP client. | ai | |
| typosquat | typosquat.levenshtein:knex | AI (typosquat): 2-edit distance from 'knex' is coincidental; package is a transport layer for @mostajs/orm, not a query builder. | ai |
Versions (showing 100 of 121)
| Version | Deps | Published |
|---|---|---|
| 2.7.3 | 11 / 15 | |
| 2.7.2 | 11 / 15 | |
| 2.7.1 | 11 / 15 | |
| 2.7.0 | 11 / 15 | |
| 2.6.10 | 11 / 15 | |
| 2.6.9 | 10 / 15 | |
| 2.6.8 | 10 / 15 | |
| 2.6.7 | 9 / 15 | |
| 2.6.6 | 9 / 15 | |
| 2.6.5 | 9 / 15 | |
| 2.6.4 | 9 / 15 | |
| 2.6.3 | 9 / 15 | |
| 2.6.2 | 9 / 15 | |
| 2.6.1 | 9 / 15 | |
| 2.6.0 | 9 / 15 | |
| 2.5.4 | 9 / 15 | |
| 2.5.3 | 9 / 15 | |
| 2.5.2 | 9 / 15 | |
| 2.5.1 | 9 / 15 | |
| 2.5.0 | 9 / 15 | |
| 2.4.5 | 9 / 15 | |
| 2.4.4 | 9 / 15 | |
| 2.4.3 | 9 / 15 | |
| 2.4.2 | 9 / 15 | |
| 2.4.1 | 9 / 15 | |
| 2.4.0 | 9 / 15 | |
| 2.3.2 | 9 / 15 | |
| 2.3.1 | 9 / 15 | |
| 2.3.0 | 9 / 15 | |
| 2.2.7 | 9 / 12 | |
| 2.2.6 | 9 / 12 | |
| 2.2.5 | 9 / 9 | |
| 2.2.4 | 9 / 9 | |
| 2.2.3 | 9 / 9 | |
| 2.2.2 | 9 / 9 | |
| 2.2.1 | 9 / 9 | |
| 2.2.0 | 9 / 9 | |
| 2.1.0 | 9 / 9 | |
| 2.0.74 | 9 / 9 | |
| 2.0.73 | 9 / 3 | |
| 2.0.72 | 9 / 3 | |
| 2.0.71 | 9 / 3 | |
| 2.0.70 | 9 / 3 | |
| 2.0.69 | 9 / 3 | |
| 2.0.68 | 9 / 3 | |
| 2.0.67 | 9 / 3 | |
| 2.0.66 | 9 / 3 | |
| 2.0.65 | 9 / 3 | |
| 2.0.64 | 9 / 3 | |
| 2.0.63 | 9 / 3 | |
| 2.0.62 | 9 / 3 | |
| 2.0.61 | 9 / 3 | |
| 2.0.60 | 9 / 3 | |
| 2.0.59 | 9 / 3 | |
| 2.0.58 | 9 / 3 | |
| 2.0.57 | 9 / 3 | |
| 2.0.56 | 9 / 3 | |
| 2.0.55 | 9 / 3 | |
| 2.0.54 | 9 / 3 | |
| 2.0.53 | 9 / 3 | |
| 2.0.52 | 9 / 3 | |
| 2.0.51 | 9 / 3 | |
| 2.0.50 | 9 / 3 | |
| 2.0.49 | 9 / 3 | |
| 2.0.48 | 9 / 3 | |
| 2.0.47 | 9 / 3 | |
| 2.0.46 | 9 / 3 | |
| 2.0.45 | 9 / 3 | |
| 2.0.44 | 9 / 3 | |
| 2.0.43 | 9 / 3 | |
| 2.0.42 | 9 / 3 | |
| 2.0.41 | 9 / 3 | |
| 2.0.40 | 9 / 3 | |
| 2.0.39 | 9 / 3 | |
| 2.0.38 | 10 / 2 | |
| 2.0.37 | 10 / 2 | |
| 2.0.36 | 10 / 2 | |
| 2.0.35 | 10 / 2 | |
| 2.0.34 | 10 / 2 | |
| 2.0.33 | 10 / 2 | |
| 2.0.32 | 9 / 2 | |
| 2.0.31 | 9 / 2 | |
| 2.0.30 | 9 / 2 | |
| 2.0.29 | 9 / 2 | |
| 2.0.28 | 9 / 2 | |
| 2.0.27 | 9 / 2 | |
| 2.0.26 | 9 / 2 | |
| 2.0.25 | 9 / 2 | |
| 2.0.24 | 9 / 2 | |
| 2.0.23 | 9 / 2 | |
| 2.0.22 | 9 / 2 | |
| 2.0.21 | 9 / 2 | |
| 2.0.20 | 9 / 2 | |
| 2.0.19 | 9 / 2 | |
| 2.0.18 | 9 / 2 | |
| 2.0.17 | 9 / 2 | |
| 2.0.16 | 9 / 2 | |
| 2.0.15 | 9 / 2 | |
| 2.0.14 | 9 / 2 | |
| 2.0.13 | 9 / 2 |
v2.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
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.6
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.5
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.4
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.3
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.2
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
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 '@mostajs/net' is 1 edit(s) away from popular package 'next'.
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 '@mostajs/net' is 1 edit(s) away from popular package 'next'.
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 '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.74
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.73
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.72
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.71
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.70
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.69
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.68
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.67
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.66
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.65
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.64
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.63
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.62
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.61
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.60
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.59
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.58
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.57
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.56
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.55
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.54
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.53
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.52
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.51
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.50
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.49
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.48
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.47
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.46
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.45
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.44
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.43
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.42
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.41
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.40
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.39
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.38
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.37
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.36
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.35
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.34
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.33
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.32
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.31
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.30
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.28
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.27
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.26
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.25
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.24
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.23
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.22
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.21
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.19
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.18
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.17
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.16
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.15
2 findingsPackage name '@mostajs/net' is 1 edit(s) away from popular package 'next'.
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 '@mostajs/net' is 1 edit(s) away from popular package 'next'.
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 '@mostajs/net' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.