@temporalio/create
Create a Temporal project from template
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Temporal SDK team has 22 approved packages; dormancy likely reflects project cadence, not takeover. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Pattern is passing process.env to child_process spawn, standard practice for CLI tools; not exfiltration. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.17.2 | 11 / 7 | |
| 1.17.1 | 11 / 7 | |
| 1.17.0 | 11 / 7 | |
| 1.16.2 | 11 / 7 | |
| 1.16.1 | 11 / 7 | |
| 1.16.0 | 11 / 7 | |
| 1.15.0 | 11 / 7 | |
| 1.14.1 | 11 / 7 | |
| 1.14.0 | 11 / 7 | |
| 1.13.2 | 11 / 7 | |
| 1.13.1 | 11 / 7 | |
| 1.13.0 | 11 / 7 | |
| 1.12.3 | 11 / 7 | |
| 1.12.2 | 11 / 7 | |
| 1.12.1 | 11 / 7 | |
| 1.12.0 | 11 / 7 | |
| 1.11.8 | 11 / 7 |
v1.17.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: temporal-sdk-team.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: temporal-sdk-team.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
3 findingsSpreading entire process.env into an object — may capture all secrets 16 | cwd: root, 17 | stdio: 'inherit', > 18 | env: { ...process.env, ADBLOCK: '1', DISABLE_OPENCOLLECTIVE: '1' }, 19 | shell: isWindows, 20 | });
Spreading entire process.env into an object — may capture all secrets 28 | cwd: root, 29 | stdio: 'inherit', > 30 | env: { ...process.env, ADBLOCK: '1', DISABLE_OPENCOLLECTIVE: '1' }, 31 | shell: isWindows, 32 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
3 findingsSpreading entire process.env into an object — may capture all secrets 16 | cwd: root, 17 | stdio: 'inherit', > 18 | env: { ...process.env, ADBLOCK: '1', DISABLE_OPENCOLLECTIVE: '1' }, 19 | shell: isWindows, 20 | });
Spreading entire process.env into an object — may capture all secrets 28 | cwd: root, 29 | stdio: 'inherit', > 30 | env: { ...process.env, ADBLOCK: '1', DISABLE_OPENCOLLECTIVE: '1' }, 31 | shell: isWindows, 32 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.0
3 findingsSpreading entire process.env into an object — may capture all secrets 16 | cwd: root, 17 | stdio: 'inherit', > 18 | env: { ...process.env, ADBLOCK: '1', DISABLE_OPENCOLLECTIVE: '1' }, 19 | shell: isWindows, 20 | });
Spreading entire process.env into an object — may capture all secrets 28 | cwd: root, 29 | stdio: 'inherit', > 30 | env: { ...process.env, ADBLOCK: '1', DISABLE_OPENCOLLECTIVE: '1' }, 31 | shell: isWindows, 32 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: temporal-sdk-team.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.