@datagrok/bio
Bioinformatics support (import/export of sequences, conversion, visualization, analysis). [See more](https://github.com/datagrok-ai/public/blob/master/packages/Bio/README.md) for details.
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:src/demo/feature_demos.ts | AI (source-diff): Long lines are inline JSON annotation data in readable TypeScript source, not obfuscation. Stable pattern for this package. | ai | |
| dependencies | unvetted-dep:@biowasm/aioli | AI (dependencies): @biowasm/aioli is a legitimate WebAssembly bioinformatics toolkit appropriate for this bioinformatics package. | ai | |
| source-diff | encoded-string-file:dist/package-test.js | AI (source-diff): Standard webpack minified bundle; samples show readable bioinformatics logic, not obfuscated payloads. | ai | |
| source-diff | encoded-string-file:dist/package.js | AI (source-diff): Standard webpack minified bundle; samples show readable bioinformatics logic, not obfuscated payloads. | ai | |
| phantom-deps | phantom-dep:file-loader | AI (phantom-deps): Webpack config reference; stable false positive. | ai | |
| phantom-deps | phantom-dep:style-loader | AI (phantom-deps): Webpack config reference; stable false positive. | ai | |
| typosquat | typosquat.levenshtein:pino | AI (typosquat): Scoped @datagrok/bio package; Levenshtein match to 'pino' is a false positive with no brand impersonation. | ai | |
| phantom-deps | phantom-dep:fastest-levenshtein | AI (phantom-deps): Build/config reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@webgpu/types | AI (phantom-deps): Type-only dependency referenced in tsconfig/webpack; stable false positive. | ai | |
| phantom-deps | phantom-dep:dayjs | AI (phantom-deps): Build/config reference in a large bioinformatics package; stable false positive. | ai | |
| phantom-deps | phantom-dep:umap-js | AI (phantom-deps): Build/config reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:css-loader | AI (phantom-deps): Webpack config reference; stable false positive. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.27.13 | 23 / 21 | |
| 2.27.12 | 23 / 21 | |
| 2.27.10 | 23 / 21 | |
| 2.27.8 | 23 / 21 | |
| 2.27.7 | 23 / 21 | |
| 2.27.6 | 23 / 21 | |
| 2.27.3 | 23 / 21 | |
| 2.27.2 | 21 / 21 | |
| 2.27.0 | 21 / 21 |
v2.27.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.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.27.8
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.27.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.27.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.27.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.