@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 21 of 121)
| Version | Deps | Published |
|---|---|---|
| 2.0.12 | 9 / 2 | |
| 2.0.11 | 9 / 2 | |
| 2.0.10 | 9 / 2 | |
| 2.0.9 | 9 / 2 | |
| 2.0.8 | 9 / 2 | |
| 2.0.7 | 9 / 2 | |
| 2.0.6 | 9 / 2 | |
| 2.0.5 | 9 / 2 | |
| 2.0.4 | 9 / 2 | |
| 2.0.3 | 9 / 2 | |
| 2.0.2 | 9 / 2 | |
| 2.0.1 | 9 / 2 | |
| 2.0.0 | 9 / 2 | |
| 1.0.7 | 9 / 2 | |
| 1.0.6 | 9 / 2 | |
| 1.0.5 | 8 / 2 | |
| 1.0.4 | 7 / 2 | |
| 1.0.3 | 7 / 2 | |
| 1.0.2 | 7 / 2 | |
| 1.0.1 | 7 / 2 | |
| 1.0.0 | 6 / 2 |
v2.0.12
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.11
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.10
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.9
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.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.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.0.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.0.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.0.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.0.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.
v1.0.7
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.
v1.0.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.
v1.0.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.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.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.
v1.0.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.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.