@k13engineering/uv-poll
File descriptor polling utilities for Node.js
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/lib/generated/uv-poll-arm64.js | AI (source-diff): Base64-encoded ELF native addon binary; NAPI symbols visible in payload, consistent with fd-polling package purpose. | ai | |
| source-diff | obfuscated-file:dist/lib/generated/uv-poll-x64.js | AI (source-diff): Base64-encoded ELF native addon binary; NAPI symbols visible in payload, consistent with fd-polling package purpose. | ai | |
| install-scripts | install-script:install | AI (install-scripts): node-gyp rebuild is the standard native addon compile step; stable for this native binding package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.0.6 | 1 / 11 | |
| 0.0.5 | 0 / 11 | |
| 0.0.3 | 0 / 11 | |
| 0.0.2 | 0 / 11 | |
| 0.0.1 | 0 / 11 |
v0.0.6
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.5
2 findingsScript: node-gyp rebuild
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.