@datagrok/sequence-translator
SequenceTranslator translates [oligonucleotide](https://en.wikipedia.org/wiki/Oligonucleotide) sequences between [different representations](https://github.com/datagrok-ai/public/tree/master/packages/SequenceTranslator#sequence-representations).
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 |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Local plugin resolution in build config, not arbitrary fetch. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Build-time webpack.config.js helper, not runtime code. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with normal Datagrok team maintainer rotation, not a takeover. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Datagrok team roster churn; publisher is a known long-standing maintainer with strong track record. | ai | |
| source-diff | obfuscated-file:dist/455.js | AI (source-diff): Webpack-bundled build output with long minified lines, not true obfuscation; matches package's chemistry domain code. | ai | |
| source-diff | obfuscated-file:dist/489.js | AI (source-diff): Standard webpack minified bundle; content is readable library code (LRU-cache, HELM), not obfuscated malware. | ai | |
| dependencies | unvetted-dep:save-svg-as-png | AI (dependencies): save-svg-as-png is a well-known SVG export utility; stable use in this bioinformatics plugin across many versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate Datagrok platform plugin; sparse README/keywords are typical for internal tooling packages. | ai | |
| phantom-deps | phantom-dep:@datagrok-libraries/tutorials | AI (phantom-deps): Datagrok internal library; referenced indirectly, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:typeahead-standalone | AI (phantom-deps): UI library referenced via config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): Type-only package loaded by convention; not directly imported at runtime. | ai | |
| phantom-deps | phantom-dep:openchemlib | AI (phantom-deps): Chemistry library used via config/indirect reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): Build-time compiler; not imported at runtime, stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:ts-loader | AI (phantom-deps): Build-time webpack loader; not imported at runtime, stable pattern for this package. | ai |
Versions (showing 49 of 49)
| Version | Deps | Published |
|---|---|---|
| 1.11.4 | 17 / 22 | |
| 1.11.3 | 17 / 22 | |
| 1.11.0 | 17 / 22 | |
| 1.10.26 | 16 / 24 | |
| 1.10.25 | 16 / 24 | |
| 1.10.24 | 16 / 24 | |
| 1.10.23 | 16 / 24 | |
| 1.10.22 | 16 / 24 | |
| 1.10.21 | 16 / 24 | |
| 1.10.20 | 16 / 24 | |
| 1.10.19 | 16 / 24 | |
| 1.10.18 | 16 / 24 | |
| 1.10.17 | 16 / 24 | |
| 1.10.16 | 16 / 24 | |
| 1.10.15 | 16 / 24 | |
| 1.10.14 | 16 / 24 | |
| 1.10.13 | 16 / 24 | |
| 1.10.12 | 16 / 24 | |
| 1.10.11 | 16 / 24 | |
| 1.10.10 | 16 / 23 | |
| 1.10.9 | 16 / 23 | |
| 1.10.8 | 16 / 23 | |
| 1.10.7 | 16 / 23 | |
| 1.10.6 | 16 / 24 | |
| 1.10.5 | 15 / 24 | |
| 1.10.4 | 15 / 24 | |
| 1.4.10 | 15 / 23 | |
| 1.4.8 | 15 / 23 | |
| 1.4.7 | 15 / 23 | |
| 1.4.6 | 15 / 23 | |
| 1.4.5 | 15 / 23 | |
| 1.4.4 | 15 / 23 | |
| 1.4.3 | 15 / 23 | |
| 1.4.2 | 15 / 23 | |
| 1.4.1 | 15 / 23 | |
| 1.4.0 | 15 / 23 | |
| 1.3.15 | 15 / 23 | |
| 1.3.14 | 15 / 24 | |
| 1.3.13 | 15 / 24 | |
| 1.3.12 | 15 / 24 | |
| 1.3.11 | 15 / 23 | |
| 1.3.10 | 15 / 23 | |
| 1.3.9 | 15 / 23 | |
| 1.3.5 | 14 / 20 | |
| 1.3.4 | 14 / 20 | |
| 1.3.3 | 14 / 20 | |
| 1.3.2 | 14 / 20 | |
| 1.3.1 | 14 / 19 | |
| 1.3.0 | 14 / 19 |
v1.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.12
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 (aparamonov_datagrok) than the most recent previously approved version (spodgrok) on 2026-04-03, but aparamonov_datagrok 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.
v1.10.11
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 (aparamonov_datagrok) than the most recent previously approved version (spodgrok) on 2026-03-04, but aparamonov_datagrok 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.
v1.10.10
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 (aparamonov_datagrok) than the most recent previously approved version (spodgrok) on 2026-03-01, but aparamonov_datagrok 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.
v1.10.9
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 (aparamonov_datagrok) than the most recent previously approved version (spodgrok) on 2026-02-26, but aparamonov_datagrok 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.
v1.10.8
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 (aparamonov_datagrok) than the most recent previously approved version (spodgrok) on 2026-02-23, but aparamonov_datagrok 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.
v1.10.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 (aparamonov_datagrok) than the most recent previously approved version (spodgrok) on 2026-02-20, but aparamonov_datagrok 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.
v1.10.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 (aparamonov_datagrok) than the most recent previously approved version (spodgrok) on 2026-02-17, but aparamonov_datagrok 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.
v1.10.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 (aparamonov_datagrok) than the most recent previously approved version (spodgrok) on 2025-12-11, but aparamonov_datagrok 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.
v1.10.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 (aparamonov_datagrok) than the most recent previously approved version (spodgrok) on 2025-11-21, but aparamonov_datagrok 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.
v1.4.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.
v1.4.8
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.
v1.4.7
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.
v1.4.6
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.
v1.4.5
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.
v1.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage 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.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.