datagrok-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 | source-size-tripled | AI (source-diff): Build artifacts bundled with SDK; consistent with Datagrok's large client package. | ai | |
| source-diff | obfuscated-file:src_datagrok_web_grok_shared_dart_js.datagrok.js | AI (source-diff): Same dart2js bundle duplicated under webpack chunk name. | ai | |
| source-diff | net-exec-file:src/datagrok/web/grok_shared.dart.js | AI (source-diff): Dart2JS bundle; network+eval patterns are compiler runtime helpers. | ai | |
| source-diff | net-exec-file:src_datagrok_web_grok_shared_dart_js.datagrok.js | AI (source-diff): Same dart2js bundle duplicated under webpack chunk name. | ai | |
| source-diff | obfuscated-file:src/datagrok/web/grok_shared.dart.js | AI (source-diff): Dart2JS compiler output signature, not hand-obfuscated malware. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): TypeScript is a build-time dependency; phantom-dep is a false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established library; missing description and repo URL are metadata gaps, not spam indicators. | ai | |
| source-diff | net-exec-file:src_datagrok_build_web_grok_shared_dart_js.datagrok.js | AI (source-diff): Same bundled dart2js content as other entries. | ai | |
| source-diff | obfuscated-file:src/datagrok/build/web/grok_shared.dart.js | AI (source-diff): dart2js-generated minified output, not obfuscation. | ai | |
| source-diff | net-exec-file:src/datagrok/build/web/grok_shared.dart.js | AI (source-diff): Bundled dart2js runtime, false-positive net+exec pattern match. | ai | |
| source-diff | net-exec-file:node-api_ts.datagrok.js | AI (source-diff): Webpack bundle chunk, not malicious code. | ai | |
| source-diff | obfuscated-file:src_datagrok_build_web_grok_shared_dart_js.datagrok.js | AI (source-diff): Webpack-wrapped dart2js bundle, minified not obfuscated. | ai | |
| phantom-deps | phantom-dep:react | AI (phantom-deps): Framework dependency loaded by convention in build/API packages; stable pattern. | ai | |
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): TypeScript types loaded by convention; stable for this package. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): Build tool loaded by convention; stable for this package. | ai | |
| phantom-deps | phantom-dep:@types/wu | AI (phantom-deps): TypeScript types loaded by convention; stable for this package. | ai |
Versions (showing 51 of 168)
| Version | Deps | Published |
|---|---|---|
| 1.27.7 | 12 / 18 | |
| 1.27.6 | 12 / 18 | |
| 1.27.5 | 12 / 18 | |
| 1.27.4 | 12 / 18 | |
| 1.27.3 | 12 / 18 | |
| 1.27.2 | 12 / 18 | |
| 1.27.1 | 12 / 18 | |
| 1.27.0 | 12 / 18 | |
| 1.26.8 | 12 / 18 | |
| 1.25.7 | 10 / 15 | |
| 1.25.6 | 10 / 15 | |
| 1.25.5 | 10 / 15 | |
| 1.25.4 | 10 / 15 | |
| 1.25.3 | 10 / 15 | |
| 1.25.2 | 10 / 15 | |
| 1.25.1 | 10 / 15 | |
| 1.25.0 | 10 / 15 | |
| 1.24.1 | 10 / 15 | |
| 1.24.0 | 10 / 15 | |
| 1.23.1 | 10 / 15 | |
| 1.23.0 | 10 / 15 | |
| 1.22.4 | 10 / 15 | |
| 1.22.3 | 10 / 15 | |
| 1.22.2 | 10 / 15 | |
| 1.22.1 | 10 / 15 | |
| 1.22.0 | 10 / 15 | |
| 1.21.4 | 10 / 15 | |
| 1.21.3 | 10 / 15 | |
| 1.21.2 | 10 / 15 | |
| 1.21.1 | 10 / 15 | |
| 1.21.0 | 10 / 15 | |
| 1.20.3 | 11 / 14 | |
| 1.20.2 | 11 / 14 | |
| 1.20.1 | 11 / 14 | |
| 1.20.0 | 11 / 14 | |
| 1.19.2 | 11 / 14 | |
| 1.19.1 | 11 / 14 | |
| 1.19.0 | 11 / 14 | |
| 1.18.9 | 11 / 15 | |
| 1.18.8 | 11 / 15 | |
| 1.18.7 | 11 / 15 | |
| 1.18.6 | 11 / 15 | |
| 1.18.5 | 11 / 15 | |
| 1.18.4 | 11 / 15 | |
| 1.18.3 | 11 / 15 | |
| 1.18.2 | 11 / 15 | |
| 1.18.1 | 11 / 15 | |
| 1.18.0 | 11 / 15 | |
| 1.17.13 | 11 / 15 | |
| 1.17.12 | 11 / 15 | |
| 1.17.11 | 11 / 15 |
v1.27.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.1
7 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
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-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.27.0
7 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
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-12, 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.26.8
7 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
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-13, 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.25.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.