@milaboratories/pl-drivers
Drivers and a low-level clients for log streaming, downloading and uploading files from and to pl
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/clients/crc32c.cjs | AI (source-diff): Long line is a CRC32C lookup table literal (Int32Array.of), not obfuscation; stable pattern for this package. | ai | |
| source-diff | obfuscated-file:dist/clients/crc32c.js | AI (source-diff): Same CRC32C lookup table literal; benign data array, not obfuscated code. | ai | |
| phantom-deps | phantom-dep:@types/fast-crc32c | AI (phantom-deps): Type-only package; not directly imported by convention, stable false positive. | ai | |
| phantom-deps | phantom-dep:upath | AI (phantom-deps): Likely used in config/build tooling; stable false positive for this package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes gRPC log response buffer; standard data handling, not obfuscation. | ai | |
| phantom-deps | phantom-dep:@grpc/grpc-js | AI (phantom-deps): gRPC transport dep used via protobuf-ts transport layer; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@protobuf-ts/plugin | AI (phantom-deps): Build-time codegen tool referenced in config scripts; not directly imported at runtime. | ai | |
| phantom-deps | phantom-dep:@protobuf-ts/grpc-transport | AI (phantom-deps): Used transitively via gRPC transport abstraction; phantom-dep heuristic false positive. | ai |
Versions (showing 51 of 157)
| Version | Deps | Published |
|---|---|---|
| 1.15.5 | 17 / 11 | |
| 1.15.4 | 17 / 11 | |
| 1.15.3 | 17 / 11 | |
| 1.15.2 | 17 / 11 | |
| 1.15.1 | 17 / 11 | |
| 1.15.0 | 17 / 11 | |
| 1.14.16 | 17 / 11 | |
| 1.14.15 | 17 / 11 | |
| 1.14.14 | 17 / 11 | |
| 1.14.13 | 17 / 11 | |
| 1.14.12 | 17 / 11 | |
| 1.14.11 | 17 / 11 | |
| 1.14.10 | 17 / 11 | |
| 1.14.9 | 17 / 11 | |
| 1.14.8 | 17 / 11 | |
| 1.14.7 | 17 / 11 | |
| 1.14.6 | 17 / 11 | |
| 1.14.5 | 17 / 11 | |
| 1.14.4 | 17 / 11 | |
| 1.14.3 | 17 / 11 | |
| 1.14.2 | 17 / 11 | |
| 1.14.1 | 17 / 11 | |
| 1.14.0 | 17 / 11 | |
| 1.13.1 | 17 / 11 | |
| 1.13.0 | 17 / 11 | |
| 1.12.23 | 17 / 11 | |
| 1.12.22 | 17 / 11 | |
| 1.12.21 | 17 / 11 | |
| 1.12.20 | 17 / 11 | |
| 1.12.19 | 17 / 11 | |
| 1.12.18 | 17 / 11 | |
| 1.12.17 | 17 / 11 | |
| 1.12.16 | 17 / 11 | |
| 1.12.15 | 17 / 11 | |
| 1.12.14 | 17 / 11 | |
| 1.12.13 | 17 / 11 | |
| 1.12.12 | 17 / 11 | |
| 1.12.11 | 17 / 11 | |
| 1.12.10 | 17 / 11 | |
| 1.12.9 | 17 / 11 | |
| 1.12.8 | 17 / 11 | |
| 1.12.7 | 17 / 11 | |
| 1.12.6 | 17 / 11 | |
| 1.11.51 | 17 / 11 | |
| 1.11.43 | 18 / 13 | |
| 1.11.42 | 18 / 13 | |
| 1.11.41 | 18 / 13 | |
| 1.11.40 | 18 / 13 | |
| 1.11.39 | 18 / 13 | |
| 1.11.38 | 18 / 13 | |
| 1.11.37 | 18 / 13 |
v1.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.51
4 findingsThis version was published by a different npm account than previous versions on 2026-02-17. This could indicate a legitimate maintainer transition or an account compromise.
Newly 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.43
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.42
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.41
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.40
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.39
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.38
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.37
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.