@servicetitan/startup
CLI to create multi-package Lerna projects with TypeScript and React
Supply chain provenance
Status for the latest visible version.
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
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 local setup script from the same org's repo; consistent across 351 versions of this build-tool package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used in postinstall.js for build-tool setup; expected pattern for this package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes a Kendo UI license key from an env variable; not a malicious payload. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Standard globalThis polyfill pattern in expose-loader runtime; not dynamic code execution of untrusted input. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Requires package.json to read engines field; not loading arbitrary user-controlled modules. | ai |
v36.1.1
2 findingsScript: node ./src/postinstall.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v35.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v35.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.