@milaboratories/pl-client
New TS/JS client for Platform API
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): Proto/REST codegen refresh explains large file count for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): openapi-fetch is a well-known, small typed fetch client, low risk. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): Known implicit runtime dependency. | ai | |
| source-diff | obfuscated-file:dist/proto-grpc/github.com/milaboratory/pl/plapi/plapiproto/api.js | AI (source-diff): Generated protobuf-ts gRPC client code, not obfuscation. | ai | |
| phantom-deps | phantom-dep:https-proxy-agent | AI (phantom-deps): Used via config, not a direct import concern. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Standard JWT payload decoding pattern; no obfuscation or dynamic execution involved. | ai | |
| phantom-deps | phantom-dep:long | AI (phantom-deps): long is a declared runtime dep used transitively by protobuf-ts; stable false positive for this package. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IP (127.0.0.1) appears only in a unit test for URL parsing — not a network call to an external host. | ai |
Versions (showing 97 of 97)
| Version | Deps | Published |
|---|---|---|
| 3.14.4 | 15 / 9 | |
| 3.14.3 | 15 / 9 | |
| 3.14.2 | 15 / 9 | |
| 3.14.1 | 15 / 9 | |
| 3.14.0 | 15 / 9 | |
| 3.13.2 | 15 / 9 | |
| 3.13.1 | 15 / 9 | |
| 3.13.0 | 15 / 9 | |
| 3.12.1 | 15 / 9 | |
| 3.12.0 | 15 / 9 | |
| 3.11.5 | 15 / 9 | |
| 3.11.4 | 15 / 9 | |
| 3.11.3 | 15 / 9 | |
| 3.11.2 | 15 / 9 | |
| 3.11.1 | 15 / 9 | |
| 3.11.0 | 15 / 9 | |
| 3.10.2 | 15 / 9 | |
| 3.10.1 | 15 / 9 | |
| 3.10.0 | 15 / 9 | |
| 3.9.2 | 15 / 9 | |
| 3.9.1 | 15 / 9 | |
| 3.9.0 | 15 / 9 | |
| 3.8.1 | 15 / 9 | |
| 3.8.0 | 15 / 9 | |
| 3.7.0 | 15 / 9 | |
| 3.6.0 | 15 / 9 | |
| 3.5.0 | 15 / 9 | |
| 3.4.2 | 15 / 9 | |
| 3.4.1 | 15 / 9 | |
| 3.4.0 | 15 / 9 | |
| 3.3.3 | 15 / 9 | |
| 3.3.2 | 15 / 9 | |
| 3.3.1 | 15 / 9 | |
| 3.3.0 | 15 / 9 | |
| 3.2.5 | 15 / 9 | |
| 3.2.4 | 15 / 9 | |
| 3.2.3 | 15 / 9 | |
| 3.2.2 | 15 / 9 | |
| 3.2.1 | 15 / 9 | |
| 3.2.0 | 15 / 9 | |
| 3.1.8 | 15 / 9 | |
| 3.1.7 | 15 / 9 | |
| 3.1.6 | 15 / 9 | |
| 3.1.5 | 15 / 9 | |
| 3.1.4 | 15 / 9 | |
| 3.1.3 | 15 / 9 | |
| 3.1.2 | 15 / 9 | |
| 3.1.1 | 15 / 9 | |
| 3.1.0 | 15 / 9 | |
| 3.0.0 | 15 / 9 | |
| 2.18.5 | 15 / 9 | |
| 2.18.4 | 15 / 9 | |
| 2.18.3 | 15 / 9 | |
| 2.18.2 | 15 / 9 | |
| 2.18.1 | 15 / 9 | |
| 2.18.0 | 15 / 9 | |
| 2.17.12 | 15 / 9 | |
| 2.17.11 | 15 / 9 | |
| 2.17.10 | 15 / 9 | |
| 2.17.9 | 15 / 9 | |
| 2.17.8 | 15 / 9 | |
| 2.17.7 | 15 / 9 | |
| 2.17.6 | 15 / 9 | |
| 2.17.5 | 15 / 9 | |
| 2.17.4 | 15 / 9 | |
| 2.17.3 | 15 / 9 | |
| 2.17.2 | 15 / 9 | |
| 2.17.1 | 15 / 9 | |
| 2.17.0 | 15 / 9 | |
| 2.16.29 | 15 / 9 | |
| 2.16.28 | 16 / 10 | |
| 2.16.27 | 16 / 10 | |
| 2.16.26 | 17 / 12 | |
| 2.16.25 | 17 / 12 | |
| 2.16.24 | 17 / 12 | |
| 2.16.23 | 17 / 12 | |
| 2.16.22 | 17 / 12 | |
| 2.16.21 | 17 / 12 | |
| 2.16.20 | 17 / 12 | |
| 2.16.19 | 17 / 12 | |
| 2.16.18 | 17 / 12 | |
| 2.16.17 | 17 / 12 | |
| 2.16.16 | 17 / 12 | |
| 2.16.15 | 17 / 12 | |
| 2.16.14 | 17 / 10 | |
| 2.16.13 | 17 / 10 | |
| 2.16.12 | 17 / 10 | |
| 2.16.11 | 17 / 10 | |
| 2.16.10 | 17 / 10 | |
| 2.16.9 | 17 / 10 | |
| 2.16.8 | 16 / 9 | |
| 2.16.7 | 16 / 9 | |
| 2.16.6 | 16 / 9 | |
| 2.16.5 | 16 / 9 | |
| 2.16.4 | 16 / 9 | |
| 2.16.3 | 16 / 9 | |
| 2.16.2 | 16 / 9 |
v3.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.9
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mike-ainsel) than the most recent previously approved version (dbolotin_mi) on 2026-03-04, but mike-ainsel is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.17.8
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mike-ainsel) than the most recent previously approved version (dbolotin_mi) on 2026-03-03, but mike-ainsel is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.17.7
3 findingsNewly 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.
This version was published by a different npm account (mike-ainsel) than the most recent previously approved version (dbolotin_mi) on 2026-02-26, but mike-ainsel is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.17.6
3 findingsNewly 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.
This version was published by a different npm account (mike-ainsel) than the most recent previously approved version (dbolotin_mi) on 2026-02-19, but mike-ainsel is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.17.5
3 findingsNewly 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.
This version was published by a different npm account (mike-ainsel) than the most recent previously approved version (dbolotin_mi) on 2026-02-19, but mike-ainsel is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.17.4
3 findingsNewly 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.
This version was published by a different npm account (mike-ainsel) than the most recent previously approved version (dbolotin_mi) on 2026-02-18, but mike-ainsel is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.17.3
3 findingsNewly 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.
This version was published by a different npm account (mike-ainsel) than the most recent previously approved version (dbolotin_mi) on 2026-02-17, but mike-ainsel is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.17.2
3 findingsNewly 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.
This version was published by a different npm account (mike-ainsel) than the most recent previously approved version (dbolotin_mi) on 2026-02-17, but mike-ainsel is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.17.1
3 findingsNewly 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.
This version was published by a different npm account (mike-ainsel) than the most recent previously approved version (dbolotin_mi) on 2026-02-17, but mike-ainsel is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.17.0
3 findingsNewly 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.
This version was published by a different npm account (mike-ainsel) than the most recent previously approved version (dbolotin_mi) on 2026-02-12, but mike-ainsel is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.16.29
3 findingsNewly 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.
This version was published by a different npm account (mike-ainsel) than the most recent previously approved version (dbolotin_mi) on 2026-02-09, but mike-ainsel is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.16.28
3 findingsNewly 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.
This version was published by a different npm account (mike-ainsel) than the most recent previously approved version (dbolotin_mi) on 2026-02-09, but mike-ainsel is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.16.27
3 findingsNewly 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.
This version was published by a different npm account (mike-ainsel) than the most recent previously approved version (dbolotin_mi) on 2026-02-09, but mike-ainsel is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.16.26
3 findingsNewly 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.
This version was published by a different npm account (mike-ainsel) than the most recent previously approved version (dbolotin_mi) on 2026-02-04, but mike-ainsel is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.16.25
2 findingsNewly 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.
v2.16.24
2 findingsNewly 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.
v2.16.23
2 findingsNewly 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.
v2.16.22
2 findingsNewly 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.
v2.16.21
2 findingsNewly 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.
v2.16.20
2 findingsNewly 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.
v2.16.19
2 findingsNewly 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.
v2.16.18
2 findingsNewly 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.
v2.16.17
2 findingsNewly 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.
v2.16.16
2 findingsNewly 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.
v2.16.15
2 findingsNewly 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.
v2.16.14
2 findingsNewly 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.
v2.16.13
2 findingsNewly 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.
v2.16.12
2 findingsNewly 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.
v2.16.11
2 findingsNewly 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.
v2.16.10
2 findingsNewly 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.
v2.16.9
2 findingsNewly 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.
v2.16.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.