@bryntum/schedulerpro-thin-trial
Bryntum Scheduler Pro JavaScript thin trial component package
2
Versions
Commercial
License
No
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
bryntumschedulerprocomponent
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 packages to protect proprietary code; stable pattern across all their trial releases. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): postinstall uses child_process only to invoke the sibling Bryntum build script; documented thin-trial install pattern. | ai |
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.