@bryntum/scheduler-trial
Bryntum Scheduler JavaScript trial component package
2
Versions
Commercial
License
Yes
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 |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall runs a build script from Bryntum's own scoped dependency; standard pattern for this commercial component package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used only to invoke @bryntum/scheduler-trial-lib/build.js; no remote code execution or user-supplied input. | ai | |
| phantom-deps | phantom-dep:@bryntum/scheduler-trial-lib | AI (phantom-deps): Dependency is used indirectly via postinstall script path resolution, not a direct import; stable false positive for this package. | 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.