@vnodes/net
@vnodes/net
8
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
rbrightline
Keywords
net
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:next | AI (typosquat): Scoped @vnodes/net is a networking lib in a monorepo; 'net' suffix matching 'next' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:nuxt | AI (typosquat): Same rationale; 2-edit distance from 'nuxt' is coincidental for a generic 'net' package. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): 2-edit distance from 'jest' is coincidental; unrelated domain. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): 2-edit distance from 'got' is coincidental for a scoped networking package. | ai | |
| typosquat | typosquat.levenshtein:knex | AI (typosquat): 2-edit distance from 'knex' is coincidental; unrelated domain. | ai | |
| phantom-deps | phantom-dep:@swc/helpers | AI (phantom-deps): @swc/helpers is a known implicit runtime dep for SWC-compiled output; stable false positive for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.1.1 | 1 / 0 | |
| 0.1.0 | 1 / 0 | |
| 0.0.37 | 1 / 0 | |
| 0.0.35 | 1 / 0 | |
| 0.0.33 | 1 / 0 | |
| 0.0.27 | 1 / 0 | |
| 0.0.25 | 1 / 0 | |
| 0.0.23 | 1 / 0 |
v0.1.1
2 findings
HIGH
typosquat.levenshtein: Possible typosquat of 'next'
typosquat
Package name '@vnodes/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.
v0.0.35
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.