@node-rs/jieba
Fastest Chinese word segmentation in Node.js
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@node-rs/jieba-linux-arm-gnueabihf | AI (phantom-deps): Standard napi-rs pattern: platform-specific optional deps loaded at runtime via @node-rs/helper, not via direct import. Same org scope. | ai | |
| phantom-deps | phantom-dep:@node-rs/jieba-win32-ia32-msvc | AI (phantom-deps): Standard napi-rs pattern: platform-specific optional deps loaded at runtime via @node-rs/helper, not via direct import. Same org scope. | ai | |
| phantom-deps | phantom-dep:@node-rs/jieba-linux-arm64-musl | AI (phantom-deps): Standard napi-rs pattern: platform-specific optional deps loaded at runtime via @node-rs/helper, not via direct import. Same org scope. | ai | |
| phantom-deps | phantom-dep:@node-rs/jieba-win32-arm64-msvc | AI (phantom-deps): Standard napi-rs pattern: platform-specific optional deps loaded at runtime via @node-rs/helper, not via direct import. Same org scope. | ai | |
| phantom-deps | phantom-dep:@node-rs/jieba-darwin-x64 | AI (phantom-deps): Standard napi-rs pattern: platform-specific optional deps loaded at runtime via @node-rs/helper, not via direct import. Same org scope. | ai | |
| phantom-deps | phantom-dep:@node-rs/jieba-freebsd-x64 | AI (phantom-deps): Standard napi-rs pattern: platform-specific optional deps loaded at runtime via @node-rs/helper, not via direct import. Same org scope. | ai | |
| phantom-deps | phantom-dep:@node-rs/jieba-darwin-arm64 | AI (phantom-deps): Standard napi-rs pattern: platform-specific optional deps loaded at runtime via @node-rs/helper, not via direct import. Same org scope. | ai | |
| phantom-deps | phantom-dep:@node-rs/jieba-android-arm64 | AI (phantom-deps): Standard napi-rs pattern: platform-specific optional deps loaded at runtime via @node-rs/helper, not via direct import. Same org scope. | ai | |
| phantom-deps | phantom-dep:@node-rs/jieba-linux-x64-gnu | AI (phantom-deps): Standard napi-rs pattern: platform-specific optional deps loaded at runtime via @node-rs/helper, not via direct import. Same org scope. | ai | |
| phantom-deps | phantom-dep:@node-rs/jieba-linux-x64-musl | AI (phantom-deps): Standard napi-rs pattern: platform-specific optional deps loaded at runtime via @node-rs/helper, not via direct import. Same org scope. | ai | |
| phantom-deps | phantom-dep:@node-rs/jieba-win32-x64-msvc | AI (phantom-deps): Standard napi-rs pattern: platform-specific optional deps loaded at runtime via @node-rs/helper, not via direct import. Same org scope. | ai | |
| phantom-deps | phantom-dep:@node-rs/jieba-linux-arm64-gnu | AI (phantom-deps): Standard napi-rs pattern: platform-specific optional deps loaded at runtime via @node-rs/helper, not via direct import. Same org scope. | ai | |
| semgrep | semgrep:child-process-execsync | AI (semgrep): execSync('ldd --version') is a hardcoded musl detection call for napi binary selection; not user-controlled and stable across all versions of this package. | ai | |
| dependencies | unvetted-dep:@node-rs/jieba-wasm32-wasi | AI (dependencies): Optional WASM/WASI platform target dependency from the same napi-rs/node-rs namespace, consistent with the package's multi-target architecture. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process is used only to run `ldd --version` for musl detection in napi binary selection — hardcoded, benign, standard napi-rs pattern across all versions. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 2.0.1 | 0 / 4 | |
| 1.10.4 | 0 / 2 | |
| 1.10.3 | 14 / 2 | |
| 1.10.2 | 14 / 2 | |
| 1.10.1 | 14 / 2 | |
| 1.10.0 | 14 / 2 | |
| 1.9.2 | 14 / 2 | |
| 1.9.1 | 14 / 2 | |
| 1.9.0 | 14 / 2 | |
| 1.8.1 | 14 / 2 | |
| 1.8.0 | 14 / 2 | |
| 1.7.2 | 13 / 2 | |
| 1.7.0 | 13 / 1 | |
| 1.6.2 | 13 / 1 | |
| 1.6.1 | 13 / 1 | |
| 1.6.0 | 13 / 1 | |
| 1.5.5 | 13 / 1 | |
| 1.5.4 | 13 / 1 | |
| 1.5.3 | 0 / 1 | |
| 1.5.2 | 13 / 1 | |
| 1.5.1 | 13 / 1 | |
| 1.4.1 | 13 / 1 | |
| 1.4.0 | 13 / 1 | |
| 1.3.1 | 13 / 1 | |
| 1.3.0 | 13 / 1 | |
| 1.2.0 | 13 / 1 | |
| 1.1.1 | 13 / 1 | |
| 1.1.0 | 10 / 1 | |
| 1.0.0 | 9 / 1 | |
| 0.6.0 | 4 / 1 | |
| 0.5.1 | 1 / 1 | |
| 0.5.0 | 1 / 1 | |
| 0.4.0 | 1 / 1 | |
| 0.3.0 | 1 / 1 | |
| 0.2.0 | 1 / 1 | |
| 0.1.1 | 1 / 1 | |
| 0.1.0 | 1 / 1 |
v2.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v1.10.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v1.10.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v1.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v1.9.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v1.9.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v1.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v1.8.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v1.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v1.7.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: broooooklyn.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
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. Consider requesting the maintainer enable provenance via CI/CD.