← Home

@mostajs/net

npm Repository Homepage

Multi-protocol transport layer for @mostajs/orm — expose entities via REST, gRPC, GraphQL, WebSocket, SSE, tRPC, MCP, OData, Arrow Flight, JSON-RPC, NATS

51
Versions
AGPL-3.0-or-later
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

apolocine

Keywords

ormtransportrestgrpcgraphqlwebsocketssemcpmulti-protocolmostajs

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 51 of 121)

View all versions
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

v2.3.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.6

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

Package name '@mostajs/net' is 1 edit(s) away from popular package 'next'.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.2.5

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

Package name '@mostajs/net' is 1 edit(s) away from popular package 'next'.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.2.4

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

Package name '@mostajs/net' is 1 edit(s) away from popular package 'next'.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.2.3

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

Package name '@mostajs/net' is 1 edit(s) away from popular package 'next'.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.2.2

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

Package name '@mostajs/net' is 1 edit(s) away from popular package 'next'.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.2.1

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

Package name '@mostajs/net' is 1 edit(s) away from popular package 'next'.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.2.0

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

Package name '@mostajs/net' is 1 edit(s) away from popular package 'next'.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.0

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

Package name '@mostajs/net' is 1 edit(s) away from popular package 'next'.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.74

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

Package name '@mostajs/net' is 1 edit(s) away from popular package 'next'.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.73

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

Package name '@mostajs/net' is 1 edit(s) away from popular package 'next'.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.72

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

Package name '@mostajs/net' is 1 edit(s) away from popular package 'next'.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.71

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

Package name '@mostajs/net' is 1 edit(s) away from popular package 'next'.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.70

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

Package name '@mostajs/net' is 1 edit(s) away from popular package 'next'.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.69

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

Package name '@mostajs/net' is 1 edit(s) away from popular package 'next'.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.68

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

Package name '@mostajs/net' is 1 edit(s) away from popular package 'next'.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.67

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

Package name '@mostajs/net' is 1 edit(s) away from popular package 'next'.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.66

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

Package name '@mostajs/net' is 1 edit(s) away from popular package 'next'.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.65

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

Package name '@mostajs/net' is 1 edit(s) away from popular package 'next'.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.64

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

Package name '@mostajs/net' is 1 edit(s) away from popular package 'next'.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.63

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

Package name '@mostajs/net' is 1 edit(s) away from popular package 'next'.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.62

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

Package name '@mostajs/net' is 1 edit(s) away from popular package 'next'.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.