@hpcc-js/dgrid
hpcc-js - Viz DGrid
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:dist/index.es6.js | AI (source-diff): Standard rollup/tsc bundle output with long lines; not obfuscated malware. Stable pattern for this package. | ai | |
| source-diff | net-exec-file:dist/index.es6.js | AI (source-diff): Network/exec pattern fires on legitimate UMD/ESM bundle boilerplate; no actual dropper behavior in sampled code. | ai | |
| source-diff | net-exec-file:dist/index.min.js | AI (source-diff): Standard terser-minified UMD bundle; UMD factory pattern triggers rule but is benign for this package. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase matches addition of pre-built dist bundles (es6+min) in new build pipeline. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() wraps a statically bundled shim import, not user input; stable pattern for this package. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 3.9.2 | 3 / 5 | |
| 3.9.1 | 3 / 5 | |
| 3.9.0 | 3 / 5 | |
| 3.8.1 | 3 / 5 | |
| 3.8.0 | 3 / 5 | |
| 3.7.9 | 3 / 5 | |
| 3.7.8 | 3 / 5 | |
| 3.7.7 | 3 / 5 | |
| 3.7.6 | 3 / 5 | |
| 3.7.5 | 3 / 5 | |
| 3.7.3 | 3 / 5 | |
| 3.7.2 | 3 / 5 | |
| 3.7.1 | 3 / 5 | |
| 3.7.0 | 3 / 5 | |
| 3.6.0 | 2 / 5 | |
| 3.5.9 | 2 / 5 | |
| 3.5.7 | 2 / 5 | |
| 3.5.6 | 2 / 5 | |
| 3.5.5 | 2 / 5 | |
| 3.5.4 | 2 / 5 | |
| 3.5.3 | 2 / 5 | |
| 3.5.2 | 2 / 5 | |
| 3.5.1 | 2 / 5 | |
| 3.5.0 | 2 / 5 | |
| 3.4.1 | 2 / 5 | |
| 3.4.0 | 2 / 5 | |
| 3.3.2 | 2 / 5 | |
| 3.3.1 | 2 / 5 | |
| 3.3.0 | 2 / 5 | |
| 3.2.11 | 2 / 5 | |
| 3.2.10 | 2 / 5 | |
| 3.2.9 | 2 / 5 | |
| 3.2.8 | 2 / 5 | |
| 3.2.7 | 2 / 5 | |
| 3.2.6 | 2 / 5 | |
| 3.2.5 | 2 / 5 | |
| 3.2.4 | 2 / 5 | |
| 3.2.3 | 2 / 5 | |
| 2.34.7 | 4 / 4 |
v3.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.34.7
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.