@bryntum/calendar-thin-trial
Bryntum Calendar JavaScript thin trial component package
5
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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
mats.bryntserasmus.ersmarker
Keywords
bryntumcalendarcomponent
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 commercial packages use javascript-obfuscator for license enforcement; this pattern is stable and intentional across all their package versions. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): postinstall uses spawnSync to invoke a sibling Bryntum build script; consistent with their thin-package build architecture. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 7.2.4 | 0 / 0 | |
| 7.2.3 | 0 / 0 | |
| 7.1.3 | 0 / 0 | |
| 7.1.2 | 0 / 0 | |
| 7.1.1 | 0 / 0 |
v7.1.3
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.2
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.
v7.1.1
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.