@bryntum/scheduler-thin-trial Commercial 2 versions

@bryntum/scheduler-thin-trial

npm Homepage

Bryntum Scheduler JavaScript thin trial component package

Versions

Commercial

License

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

mats.bryntserasmus.ersmarker

Keywords

bryntumschedulercomponent

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 intentionally obfuscates trial package JS for license enforcement; stable pattern across all their trial packages.	ai	2026/04/29
semgrep	semgrep:child-process-import	AI (semgrep): postinstall uses spawnSync to run a sibling @bryntum build script; documented thin-package pattern, not arbitrary code execution.	ai	2026/04/29

Versions (showing 2 of 2)

Version	Deps	Published
7.2.4	0 / 0	2026-04-27
7.2.3	0 / 0	2026-04-09

v7.2.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.