@vitessce/statistical-plots
Supply chain provenance
Status for the latest visible version.
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-DKGZofDL.js | AI (source-diff): Minified Vite bundle of React/vitessce code, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/lerc-DvHuJtok.js | AI (source-diff): Vendored Esri LERC decoder, minified not obfuscated. | ai | |
| source-diff | net-exec-file:dist/index-DKGZofDL.js | AI (source-diff): False positive on bundled UI code with fetch/eval patterns from libs like LERC decoder. | ai | |
| source-diff | net-exec-file:dist/index-9fVs96zH.js | AI (source-diff): Bundled app code (React/vega) flagged by pattern match, no dropper behavior found. | ai | |
| source-diff | obfuscated-file:dist/lerc-bi6D1HS5.js | AI (source-diff): Bundled LERC decoder library code, minified not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/index-9fVs96zH.js | AI (source-diff): Vite/rollup bundle output, not true obfuscation; large monorepo package. | ai | |
| source-diff | obfuscated-file:dist/index-ButG05zl.js | AI (source-diff): Standard Vite bundle output, not true obfuscation. | ai | |
| source-diff | obfuscated-file:dist/lerc-CZimPdvH.js | AI (source-diff): Bundled lerc/pako decoder library, minified not obfuscated. | ai | |
| source-diff | net-exec-file:dist/index-ButG05zl.js | AI (source-diff): Bundled React/lerc/pako code, no actual dropper behavior. | ai | |
| source-diff | obfuscated-file:dist/index-SvDouI4P.js | AI (source-diff): Vite/rollup bundle output, not obfuscation; contains legitimate imports and lib code. | ai | |
| source-diff | obfuscated-file:dist/lerc-dL8eLHoB.js | AI (source-diff): Bundled third-party LERC decoder (Esri, Apache-licensed), not obfuscated malware. | ai | |
| source-diff | net-exec-file:dist/index-SvDouI4P.js | AI (source-diff): Large bundled file triggers pattern match; no evidence of dropper behavior. | ai | |
| source-diff | obfuscated-file:dist/index-CvvREgcn.js | AI (source-diff): Vite/rollup bundle output for a legit UI package, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/lerc-DqbSitEX.js | AI (source-diff): Bundled Esri LERC decoder library, not obfuscation. | ai | |
| source-diff | net-exec-file:dist/index-CvvREgcn.js | AI (source-diff): Bundled React/vis code; no dropper/loader behavior evident in sample. | ai | |
| source-diff | encoded-string-file:dist/index.js | AI (source-diff): Hex-encoded color palette data (d3/vega colormaps), not obfuscated payload. | ai | |
| source-diff | net-exec-file:dist/index-C1rdPiFE.js | AI (source-diff): Bundled React/vis library code; no malicious network+exec behavior found. | ai | |
| source-diff | obfuscated-file:dist/lerc-CwNw9uz4.js | AI (source-diff): Bundled lerc/pako codec dependency, minified not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/index-C1rdPiFE.js | AI (source-diff): Vite/Rollup bundled output, not obfuscation; consistent with package's build process. | ai | |
| source-diff | obfuscated-file:dist/index-q44JSarg.js | AI (source-diff): Bundled/minified vite output, not obfuscation; matches legit library code. | ai | |
| source-diff | net-exec-file:dist/index-q44JSarg.js | AI (source-diff): False positive from bundler pattern-matching, no actual dropper behavior. | ai | |
| source-diff | obfuscated-file:dist/lerc-_NCoDm-Z.js | AI (source-diff): Bundled LERC/pako decoder library, minified not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/index-DQNZPvU7.js | AI (source-diff): Vite/Rollup bundle output, not obfuscation; matches monorepo build pipeline. | ai | |
| source-diff | obfuscated-file:dist/lerc-DqyheC4U.js | AI (source-diff): Bundled Esri LERC decoder library, legitimate dependency, not obfuscation. | ai | |
| source-diff | net-exec-file:dist/index-DQNZPvU7.js | AI (source-diff): Bundled React/data-loading code, no fetched-binary or exfil behavior found. | ai | |
| source-diff | obfuscated-file:dist/index-BdzAC4Cq.js | AI (source-diff): Vite/rollup bundle output, not true obfuscation; contains recognizable React/vitessce source. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Long-standing monorepo subpackage convention, not indicative of risk. | ai | |
| source-diff | obfuscated-file:dist/lerc-Bvt14Cst.js | AI (source-diff): Vendored Esri LERC decoder library, minified not obfuscated. | ai | |
| source-diff | net-exec-file:dist/index-BdzAC4Cq.js | AI (source-diff): Bundled app code triggers pattern match; no concrete malicious network/exec behavior identified. | ai | |
| source-diff | net-exec-file:dist/index-BmYvVUY8.js | AI (source-diff): False positive from bundled UI framework code, no actual dropper behavior present. | ai | |
| source-diff | obfuscated-file:dist/lerc-DdM66WTL.js | AI (source-diff): Bundled third-party lerc/pako decoder library, standard minified vendor code. | ai | |
| source-diff | obfuscated-file:dist/index-BmYvVUY8.js | AI (source-diff): Vite/rollup bundle output, not true obfuscation; matches package's build process. | ai | |
| source-diff | obfuscated-file:dist/index-Bww8vUPc.js | AI (source-diff): Vite-bundled build output, not true obfuscation; sample shows readable React/Vitessce imports. | ai | |
| source-diff | obfuscated-file:dist/lerc-CEyFtJYR.js | AI (source-diff): Bundled third-party lerc/pako decoder library, not obfuscated malware. | ai | |
| source-diff | net-exec-file:dist/index-Bww8vUPc.js | AI (source-diff): False positive from bundler pattern-match; no actual network+exec malware behavior in sample. | ai | |
| phantom-deps | phantom-dep:d3-format | AI (phantom-deps): d3-format is a legitimate declared dependency in package.json for this D3-based plotting package. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 4.0.0 | 19 / 4 | |
| 3.9.11 | 19 / 4 | |
| 3.9.10 | 19 / 4 | |
| 3.9.9 | 19 / 4 | |
| 3.9.8 | 19 / 4 | |
| 3.9.7 | 19 / 4 | |
| 3.9.6 | 19 / 4 | |
| 3.9.5 | 19 / 4 | |
| 3.9.4 | 19 / 4 | |
| 3.9.3 | 19 / 4 | |
| 3.9.2 | 19 / 4 | |
| 3.9.1 | 19 / 4 | |
| 3.9.0 | 19 / 4 | |
| 3.8.13 | 19 / 4 | |
| 3.8.10 | 19 / 4 | |
| 3.8.9 | 19 / 4 | |
| 3.8.8 | 19 / 4 | |
| 3.8.7 | 19 / 4 | |
| 3.8.6 | 19 / 4 | |
| 3.4.6 | 15 / 3 | |
| 3.4.5 | 15 / 3 | |
| 3.4.4 | 15 / 3 | |
| 3.4.3 | 15 / 3 | |
| 3.4.2 | 15 / 3 | |
| 3.4.1 | 15 / 3 | |
| 3.4.0 | 15 / 3 |
v4.0.0
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 source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.9.6
5 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 source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (keller-mark) on 2026-03-26, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v3.9.5
5 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 source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (keller-mark) on 2026-02-23, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v3.9.4
5 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 source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (keller-mark) on 2026-02-11, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v3.9.3
5 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 source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (keller-mark) on 2026-02-11, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v3.9.2
5 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 source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (keller-mark) on 2026-02-05, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v3.9.1
5 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 source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (keller-mark) on 2026-01-27, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v3.9.0
5 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 source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (keller-mark) on 2026-01-16, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v3.8.13
5 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 source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (keller-mark) on 2025-12-14, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v3.8.10
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 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.
v3.8.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.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 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.
v3.8.6
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 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.
v3.4.6
2 findingsModified file contains 2 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.
v3.4.5
2 findingsModified file contains 2 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.
v3.4.4
2 findingsModified file contains 2 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.
v3.4.3
2 findingsModified file contains 2 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.
v3.4.2
2 findingsModified file contains 2 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.
v3.4.1
2 findingsModified file contains 2 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.
v3.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.