@syncbridge/net
SyncBridge builtin net (socket) extensions
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@serialport/bindings-interface | AI (phantom-deps): Optional pluggable dependency; referenced in config, not direct import. | ai | |
| phantom-deps | phantom-dep:@pinggy/pinggy | AI (phantom-deps): Optional pluggable dependency; referenced in config, not direct import. | ai | |
| phantom-deps | phantom-dep:fast-tokenizer | AI (phantom-deps): Optional pluggable dependency; referenced in config, not direct import. | ai | |
| phantom-deps | phantom-dep:lightning-pool | AI (phantom-deps): Optional pluggable dependency; referenced in config, not direct import. | ai | |
| phantom-deps | phantom-dep:putil-varhelpers | AI (phantom-deps): Optional pluggable dependency; referenced in config, not direct import. | ai | |
| phantom-deps | phantom-dep:file-stream-rotator | AI (phantom-deps): Optional pluggable dependency; referenced in config, not direct import. | ai | |
| phantom-deps | phantom-dep:hl7v2 | AI (phantom-deps): Optional pluggable dependency; referenced in config, not direct import. | ai | |
| phantom-deps | phantom-dep:kafkajs | AI (phantom-deps): Optional pluggable dependency; referenced in config, not direct import. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): Optional pluggable dependency; referenced in config, not direct import. | ai | |
| phantom-deps | phantom-dep:oracledb | AI (phantom-deps): Optional pluggable dependency; referenced in config, not direct import. | ai | |
| phantom-deps | phantom-dep:hl7v2-net | AI (phantom-deps): Optional pluggable dependency; referenced in config, not direct import. | ai | |
| phantom-deps | phantom-dep:serialport | AI (phantom-deps): Optional pluggable dependency; referenced in config, not direct import. | ai | |
| phantom-deps | phantom-dep:@sqb/oracle | AI (phantom-deps): Optional pluggable dependency; referenced in config, not direct import. | ai | |
| phantom-deps | phantom-dep:@ngrok/ngrok | AI (phantom-deps): Optional pluggable dependency; referenced in config, not direct import. | ai | |
| phantom-deps | phantom-dep:@sqb/connect | AI (phantom-deps): Optional pluggable dependency; referenced in config, not direct import. | ai | |
| phantom-deps | phantom-dep:@sqb/postgres | AI (phantom-deps): Optional pluggable dependency; referenced in config, not direct import. | ai | |
| typosquat | typosquat.levenshtein:nuxt | AI (typosquat): Same rationale — scoped package in a coherent org, not impersonating nuxt. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped package; no impersonation of jest. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped package; no impersonation of got. | ai | |
| typosquat | typosquat.levenshtein:knex | AI (typosquat): Scoped package; no impersonation of knex. | ai | |
| typosquat | typosquat.levenshtein:next | AI (typosquat): Scoped @syncbridge org package; Levenshtein match to 'next' is coincidental, not a typosquat. | ai |
Versions (showing 62 of 62)
| Version | Deps | Published |
|---|---|---|
| 0.13.2 | 5 / 0 | |
| 0.13.0 | 5 / 0 | |
| 0.12.0 | 5 / 0 | |
| 0.11.0 | 5 / 0 | |
| 0.10.5 | 5 / 0 | |
| 0.10.4 | 5 / 0 | |
| 0.10.3 | 5 / 0 | |
| 0.10.2 | 5 / 0 | |
| 0.10.1 | 5 / 0 | |
| 0.10.0 | 5 / 0 | |
| 0.9.5 | 5 / 0 | |
| 0.9.4 | 5 / 0 | |
| 0.9.3 | 5 / 0 | |
| 0.9.2 | 5 / 0 | |
| 0.9.1 | 5 / 0 | |
| 0.9.0 | 5 / 0 | |
| 0.8.0 | 5 / 0 | |
| 0.7.6 | 5 / 0 | |
| 0.7.5 | 5 / 0 | |
| 0.7.4 | 5 / 0 | |
| 0.7.3 | 5 / 0 | |
| 0.7.2 | 5 / 0 | |
| 0.7.0 | 5 / 0 | |
| 0.6.2 | 4 / 0 | |
| 0.6.1 | 4 / 0 | |
| 0.6.0 | 4 / 0 | |
| 0.5.0 | 4 / 0 | |
| 0.4.37 | 20 / 0 | |
| 0.4.36 | 20 / 0 | |
| 0.4.35 | 20 / 0 | |
| 0.4.34 | 20 / 0 | |
| 0.4.33 | 20 / 0 | |
| 0.4.32 | 20 / 0 | |
| 0.4.31 | 20 / 0 | |
| 0.4.30 | 20 / 0 | |
| 0.4.29 | 20 / 0 | |
| 0.4.27 | 20 / 0 | |
| 0.4.26 | 20 / 0 | |
| 0.4.25 | 20 / 0 | |
| 0.4.24 | 20 / 0 | |
| 0.4.23 | 20 / 0 | |
| 0.4.22 | 20 / 0 | |
| 0.4.21 | 20 / 0 | |
| 0.4.20 | 20 / 0 | |
| 0.4.19 | 20 / 0 | |
| 0.4.18 | 20 / 0 | |
| 0.4.17 | 20 / 0 | |
| 0.4.16 | 20 / 0 | |
| 0.4.15 | 20 / 0 | |
| 0.4.14 | 20 / 0 | |
| 0.4.13 | 20 / 0 | |
| 0.4.12 | 20 / 0 | |
| 0.4.11 | 20 / 0 | |
| 0.4.10 | 20 / 0 | |
| 0.4.9 | 20 / 0 | |
| 0.4.8 | 20 / 0 | |
| 0.4.7 | 20 / 0 | |
| 0.4.6 | 20 / 0 | |
| 0.4.5 | 20 / 0 | |
| 0.4.4 | 20 / 0 | |
| 0.4.3 | 20 / 0 | |
| 0.4.1 | 20 / 0 |
v0.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
2 findingsPackage name '@syncbridge/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.
v0.10.4
2 findingsPackage name '@syncbridge/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.
v0.10.3
2 findingsPackage name '@syncbridge/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.
v0.10.1
2 findingsPackage name '@syncbridge/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.
v0.10.0
2 findingsPackage name '@syncbridge/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.
v0.9.5
2 findingsPackage name '@syncbridge/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.
v0.9.4
2 findingsPackage name '@syncbridge/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.
v0.9.3
2 findingsPackage name '@syncbridge/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.
v0.9.2
2 findingsPackage name '@syncbridge/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.
v0.9.1
2 findingsPackage name '@syncbridge/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.
v0.9.0
2 findingsPackage name '@syncbridge/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.
v0.8.0
2 findingsPackage name '@syncbridge/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.
v0.7.6
2 findingsPackage name '@syncbridge/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.
v0.7.5
2 findingsPackage name '@syncbridge/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.
v0.7.4
2 findingsPackage name '@syncbridge/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.
v0.7.3
2 findingsPackage name '@syncbridge/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.
v0.7.2
2 findingsPackage name '@syncbridge/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.
v0.7.0
2 findingsPackage name '@syncbridge/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.
v0.6.2
2 findingsPackage name '@syncbridge/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.
v0.6.1
2 findingsPackage name '@syncbridge/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.
v0.6.0
2 findingsPackage name '@syncbridge/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.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.