@dbos-inc/create
Tool for performing project initialization 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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used only in a dev template script for starting a local Postgres Docker container; not a runtime or install-time risk. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scaffolding/create tool; sparse README and no keywords are expected for this package type. | ai | |
| phantom-deps | phantom-dep:update-notifier | AI (phantom-deps): update-notifier referenced in config but not directly imported; stable false positive for this package. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 4.19.8 | 6 / 5 | |
| 4.18.10 | 6 / 5 | |
| 4.17.6 | 6 / 5 | |
| 4.16.7 | 6 / 5 | |
| 4.15.5 | 6 / 5 | |
| 4.14.6 | 6 / 5 | |
| 4.13.5 | 6 / 5 | |
| 4.12.9 | 6 / 5 | |
| 4.11.11 | 6 / 5 | |
| 4.10.15 | 6 / 5 | |
| 4.9.11 | 6 / 5 | |
| 4.8.8 | 6 / 5 | |
| 4.7.9 | 6 / 5 | |
| 4.6.11 | 6 / 5 | |
| 4.5.13 | 6 / 5 | |
| 4.4.9 | 6 / 5 | |
| 4.2.6 | 6 / 5 | |
| 4.1.6 | 6 / 5 | |
| 4.0.2 | 6 / 5 |
v4.19.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.16.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.