@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, 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 |
|---|---|---|---|---|
| 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 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 1.21.1 | 11 / 5 | |
| 1.21.0 | 11 / 5 | |
| 1.20.3 | 11 / 5 | |
| 1.20.2 | 11 / 5 | |
| 1.20.1 | 11 / 5 | |
| 1.20.0 | 11 / 5 | |
| 1.19.1 | 11 / 5 | |
| 1.19.0 | 11 / 5 | |
| 1.18.2 | 11 / 5 | |
| 1.18.1 | 11 / 5 | |
| 1.18.0 | 11 / 5 | |
| 1.17.5 | 11 / 7 | |
| 1.17.4 | 11 / 7 | |
| 1.17.3 | 11 / 5 | |
| 1.17.2 | 11 / 7 | |
| 1.17.1 | 11 / 7 | |
| 1.17.0 | 11 / 7 | |
| 1.16.3 | 11 / 7 | |
| 1.16.2 | 11 / 7 | |
| 1.16.1 | 11 / 7 | |
| 1.16.0 | 11 / 7 | |
| 1.15.1 | 11 / 7 | |
| 1.15.0 | 11 / 7 | |
| 1.14.2 | 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 | |
| 1.11.7 | 11 / 7 | |
| 1.11.6 | 11 / 7 | |
| 1.11.5 | 11 / 7 | |
| 1.11.4 | 11 / 7 | |
| 1.11.3 | 11 / 7 | |
| 1.11.2 | 11 / 7 | |
| 1.11.1 | 11 / 7 | |
| 1.11.0 | 11 / 7 | |
| 1.10.3 | 11 / 7 | |
| 1.10.2 | 11 / 7 | |
| 1.10.1 | 11 / 7 | |
| 1.10.0 | 11 / 7 |
v1.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.