apexcharts
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| license | uncommon-license:SEE LICENSE IN LICENSE | AI (license): Custom license file reference is stable for this package. | ai | |
| source-diff | obfuscated-file:dist/features/morph.common.js | AI (source-diff): Standard minified dist bundle for new morph feature; consistent with build tooling across this package. | ai | |
| source-diff | obfuscated-file:dist/features/annotations.common.js | AI (source-diff): Standard minified dist bundle; chart annotation logic. | ai | |
| source-diff | obfuscated-file:dist/apexcharts.ssr.common.js | AI (source-diff): Standard minified SSR bundle for apexcharts. | ai | |
| source-diff | obfuscated-file:dist/area.common.js | AI (source-diff): Standard minified dist bundle; area chart logic. | ai | |
| source-diff | obfuscated-file:dist/bar.common.js | AI (source-diff): Standard minified dist bundle; bar chart logic. | ai | |
| source-diff | obfuscated-file:dist/boxPlot.common.js | AI (source-diff): Standard minified dist bundle; boxPlot chart logic. | ai | |
| source-diff | obfuscated-file:dist/bubble.common.js | AI (source-diff): Standard minified dist bundle; bubble chart logic. | ai | |
| source-diff | obfuscated-file:dist/candlestick.common.js | AI (source-diff): Standard minified dist bundle; candlestick chart logic. | ai | |
| source-diff | obfuscated-file:dist/core.common.js | AI (source-diff): Standard minified dist bundle; core chart logic. | ai | |
| source-diff | obfuscated-file:dist/donut.common.js | AI (source-diff): Standard minified dist bundle; donut chart logic. | ai | |
| source-diff | obfuscated-file:dist/features/exports.common.js | AI (source-diff): Standard minified dist bundle; export feature logic. | ai | |
| source-diff | obfuscated-file:dist/heatmap.common.js | AI (source-diff): Standard minified dist bundle; heatmap chart logic. | ai | |
| source-diff | obfuscated-file:dist/features/keyboard.common.js | AI (source-diff): Standard minified dist bundle; keyboard feature logic. | ai | |
| source-diff | obfuscated-file:dist/features/legend.common.js | AI (source-diff): Standard minified dist bundle; legend feature logic. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Major version restructuring into tree-shakeable chart-type entry points. | ai | |
| provenance | publisher-changed | AI (provenance): Migration to GitHub Actions CI/CD with SLSA provenance; legitimate transition. | ai | |
| source-diff | obfuscated-file:dist/column.common.js | AI (source-diff): Standard minified dist bundle; column chart logic. | ai | |
| source-diff | obfuscated-file:dist/features/all.common.js | AI (source-diff): Standard minified dist bundle for a charting library; no suspicious payload. | ai | |
| phantom-deps | phantom-dep:@yr/monotone-cubic-spline | AI (phantom-deps): Legitimate runtime dep used in bundled output; phantom-dep heuristic fires because it's not directly imported in source scan. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Used in SSR hydration to deserialize chart config; legitimate pattern for this charting library. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 5.14.0 | 0 / 32 | |
| 5.13.0 | 0 / 32 | |
| 5.12.0 | 0 / 32 | |
| 5.11.0 | 0 / 32 | |
| 5.10.6 | 0 / 32 | |
| 5.10.5 | 0 / 32 | |
| 5.4.0 | 1 / 30 | |
| 5.3.6 | 6 / 47 | |
| 5.3.5 | 6 / 47 | |
| 5.3.4 | 6 / 47 | |
| 5.3.3 | 6 / 47 | |
| 5.3.2 | 6 / 47 | |
| 5.3.1 | 6 / 47 | |
| 5.3.0 | 6 / 47 | |
| 5.2.0 | 6 / 47 | |
| 5.1.0 | 6 / 47 | |
| 5.0.0 | 6 / 47 |
v5.14.0
2 findingsNewly 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.
v5.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.10.5
17 findingsThis version was published by a different npm account than previous versions on 2026-04-06. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
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.
v5.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.