@bryntum/schedulerpro-thin-trial
Bryntum Scheduler Pro 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, so a manually published version cannot be tied back to a reviewed commit.
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 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 |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 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.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.