@bryntum/engine-thin-trial
Bryntum Engine JavaScript thin trial component package
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 |
|---|---|---|---|---|
| semgrep | semgrep:obfuscation-while-true | AI (semgrep): Bryntum ships intentionally obfuscated trial bundles to protect commercial IP; stable pattern across all their packages. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Fires inside obfuscated bundle; part of the obfuscator runtime, not a standalone exploit vector. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): postinstall.cjs uses spawnSync to build companion @bryntum/engine-trial-lib; expected thin-trial install pattern. | ai | |
| provenance | no-provenance | AI (provenance): Bryntum publishes commercial packages without Sigstore provenance; consistent across their registry presence. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 7.3.1 | 0 / 0 | |
| 7.3.0 | 0 / 0 | |
| 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.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.