ApexCharts 4.7.0 source comparison

This report compares tracked source files in the WestCoast Charts 1.1.1 source commit with the published ApexCharts 4.7.0 source package. It measures file identity and source-line differences. It is not a copyright opinion, license determination, security assessment, or quality score.

#Source pins

• Target library source commit: 56a7708437f1932ceea3b742db7268a6857133cf, as recorded in the release artifact manifest. The public Core export is 89131079f037e29806afb66d5770d9f715570841.
• Baseline: published apexcharts@4.7.0 tarball from the npm registry, whose SHA-512 SRI is sha512-iZSrrBGvVlL+nt2B1NpqfDuBZ9jX61X9I2+XV0hlYXHtTwhwLTHDKGXjNXAgFBDLuvSYCB/rq2nPWVPRv2DrGA==.
• npm metadata's source gitHead is 2c72f8299dba81dddbb50d2b8178163efbde2305; its 140 tracked src/** files match the tarball byte-for-byte. The official GitHub v4.7.0 tag resolves to 1e93a0d47b834111cf616fb6c78a263bbae7c1d8; it has the same source paths, with one file difference from the npm artifact (src/apexcharts.js). The comparison uses the integrity-verified npm artifact as its primary baseline and records the tag separately.

#What the file and line counts show

The npm baseline has 140 src/** files and 35,877 lines. Of those paths, 139 exist at the WestCoast Charts target commit: 68 files are byte-identical and 71 are modified at the same path. One baseline file, src/assets/apexcharts.css, is absent. The full target source checkout has 414 files and 101,216 lines, including optional and separately distributed modules.

On same-path modified files, an aligned line-block matcher estimates 30,457 baseline lines remain; paired with 3,855 lines from byte-identical files, that is 34,312 of 35,877 baseline lines (95.64%). This is a textual similarity estimate, not a statement that the lines are independently authored or semantically unchanged. Formatting and repeated lines affect it.

Raw Git Myers diff counts provide an independent addition/deletion measure. Across modified same-path files the diff records 4,154 additions and 778 deletions. Total lines reconcile exactly: 35,877 baseline − 750 lines in removed CSS + 62,713 lines in target-only files + 4,154 additions − 778 deletions = 101,216 target lines.

The last row is a directory-based source scope, not the built Core bundle. It includes optional modules and WCC additions under those paths. It shows substantial line continuity: the 97.67% is the share of baseline lines matched in this scope, while 60.20% is the same line-match estimate divided by the current lines in those directories. Neither number measures gzip weight or risk.

Selected module-level detail (all module groups are in the CSV):

#Third-party and non-code files

Third-party SVG/math implementations are separated from Apex-origin files. The baseline has three such files (901 lines): monotone-cubic.js is byte-identical and names yr.no in its MIT header; Treemap-squared.js is modified and identifies Imran Ghory; svg.pathmorphing.js is modified and identifies its own author. The target also adds svg-lite.js, whose header documents its SVG.js 3.2 origin and MIT license. These are counted separately from the selected core-related source line totals.

The baseline contains 44 locale files: 43 remain byte-identical, one is modified. Of 17 baseline assets, 16 icons remain byte-identical; the 750-line apexcharts.css is removed. CSS, locales, and assets are not used to infer engine authorship.

The full source checkout has 26,472 lines in src/premium/; per-file Premium paths and hashes are omitted from the public machine report. The public report retains only aggregate counts needed for the full-source denominator. The public MIT Core export does not include that separate Premium source.

#Limits and downloads

A modified file may preserve most upstream line blocks while containing important behavioral changes. Conversely, a small new block can be critical. Line counts do not measure security risk, code ownership, semantic independence, test coverage, or production bundle size. This report makes none of those claims. The public Core export does not contain the complete source checkout used for the comparison. Independent full recomputation therefore requires an authorized local checkout of the recorded source commit; the public download includes the report inputs, hashes, and method, not restricted source files.

• Machine-readable JSON
• Per-module CSV
• Reproduction script · instructions