← Home

@datagrok/helm

npm Repository Homepage

Provides support for HELM notation (importing, detecting, rendering, conversion).

4
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

aparamonov_datagrokskalkindrizhinappolovyi_datagrokaleksashka_11

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff encoded-string-file:dist/package-test.js AI (source-diff): Webpack bundle; samples show readable domain logic, not obfuscated payloads. Stable pattern for this package. ai
source-diff encoded-string-file:dist/package.js AI (source-diff): Webpack bundle; samples show readable domain logic, not obfuscated payloads. Stable pattern for this package. ai
typosquat typosquat.levenshtein:helmet AI (typosquat): HELM is a bioinformatics notation standard; @datagrok/helm is not a typosquat of helmet. ai
semgrep semgrep:eval-usage AI (semgrep): eval() is in vendored Pistoia.HELM library for function validation, not remote code execution. ai
phantom-deps phantom-dep:dayjs AI (phantom-deps): dayjs is a declared runtime dep; phantom-dep heuristic false positive for this package. ai
phantom-deps phantom-dep:@datagrok-libraries/helm-web-editor AI (phantom-deps): Declared runtime dep used via config/webpack; phantom-dep heuristic false positive. ai

Versions (showing 4 of 4)

Version Deps Published
2.13.8 11 / 19
2.13.7 11 / 19
2.13.6 11 / 19
2.13.5 11 / 19

v2.13.8

3 findings
HIGH Long encoded string in modified file: dist/package-test.js source-diff

Modified file contains 665 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

HIGH Long encoded string in modified file: dist/package.js source-diff

Modified file contains 665 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.13.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.13.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.13.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.