@bryntum/gantt-vue-3-thin
Vue 3 wrappers for Bryntum Gantt JavaScript component
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:lib/chunks/B8Nlig6n.js | AI (source-diff): Bryntum commercial SDK ships bundled chunks; long lines are from Rollup bundling, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/chunks/BADQ7Hh-.js | AI (source-diff): Same pattern as above — standard Rollup chunk for BryntumGantt Vue wrapper. | ai | |
| source-diff | obfuscated-file:lib/chunks/DA8vJbIq.js | AI (source-diff): Standard Vite/Rollup build output for a Vue 3 component wrapper; not obfuscated, just minified with long prop-definition lines. | ai | |
| source-diff | obfuscated-file:lib/chunks/DFy-NnPl.js | AI (source-diff): Same pattern — bundled Vue 3 wrapper chunk, readable ES module imports, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:lib/chunks/BCYn5ruh.js | AI (source-diff): Minified Vite/Rollup build chunk for Vue wrapper; readable ES module code, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:lib/chunks/CjDPUhTJ.js | AI (source-diff): Same pattern — standard bundler output for BryntumGanttBase Vue component wrapper. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 7.2.4 | 0 / 0 | |
| 7.2.3 | 0 / 0 | |
| 7.2.2 | 0 / 0 | |
| 7.2.1 | 0 / 0 | |
| 7.2.0 | 0 / 0 | |
| 7.1.3 | 0 / 0 | |
| 7.1.2 | 0 / 0 | |
| 7.1.1 | 0 / 0 |
v7.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.2
3 findingsNewly 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.1
3 findingsNewly 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
3 findingsNewly 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.3
3 findingsNewly 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.