@budibase/string-templates
Handlebars wrapper for Budibase templating.
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): christos-budibase is an established Budibase org publisher; internal team rotation, not a takeover signal. | ai | |
| phantom-deps | phantom-dep:lodash.clonedeep | AI (phantom-deps): Declared and used; phantom-dep heuristic is imperfect for bundled/re-exported deps. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Budibase monorepo with 3112 versions; org publisher account; no content changes from prior approved version. | ai | |
| dependencies | unvetted-dep:@budibase/vm-browserify | AI (dependencies): Same org scope (@budibase); internal dependency stable across Budibase monorepo versions. | ai | |
| dependencies | unvetted-dep:handlebars | AI (dependencies): handlebars is a well-known templating library; pinned to 4.7.9 which is the latest stable release. | ai | |
| phantom-deps | phantom-dep:@budibase/vm-browserify | AI (phantom-deps): Same-org scoped dep; likely bundled via rollup rather than directly imported. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Budibase monorepo package; sparse README and missing metadata are expected for scoped internal packages. | ai | |
| phantom-deps | phantom-dep:@budibase/handlebars-helpers | AI (phantom-deps): Same-org scoped dep; likely bundled via rollup rather than directly imported. | ai |
Versions (showing 51 of 107)
| Version | Deps | Published |
|---|---|---|
| 3.38.5 | 4 / 11 | |
| 3.38.4 | 4 / 11 | |
| 3.38.2 | 4 / 11 | |
| 3.38.1 | 4 / 11 | |
| 3.38.0 | 4 / 11 | |
| 3.37.5 | 4 / 11 | |
| 3.37.4 | 4 / 11 | |
| 3.37.3 | 4 / 11 | |
| 3.37.2 | 4 / 11 | |
| 3.37.1 | 4 / 11 | |
| 3.37.0 | 4 / 11 | |
| 3.36.5 | 4 / 11 | |
| 3.36.3 | 4 / 11 | |
| 3.35.3 | 4 / 11 | |
| 3.35.2 | 4 / 11 | |
| 3.35.1 | 4 / 11 | |
| 3.35.0 | 4 / 11 | |
| 3.34.11 | 4 / 11 | |
| 3.34.5 | 4 / 11 | |
| 3.34.2 | 5 / 11 | |
| 3.33.5 | 5 / 11 | |
| 3.23.30 | 5 / 11 | |
| 3.23.1 | 5 / 11 | |
| 3.23.0 | 5 / 11 | |
| 3.22.7 | 5 / 11 | |
| 3.22.6 | 5 / 11 | |
| 3.22.4 | 5 / 11 | |
| 3.22.3 | 5 / 11 | |
| 3.22.2 | 5 / 11 | |
| 3.22.1 | 5 / 11 | |
| 3.22.0 | 5 / 11 | |
| 3.21.3 | 5 / 11 | |
| 3.21.1 | 5 / 11 | |
| 3.20.15 | 5 / 11 | |
| 3.20.14 | 5 / 11 | |
| 3.20.13 | 5 / 11 | |
| 3.20.12 | 5 / 11 | |
| 3.20.9 | 5 / 11 | |
| 3.20.8 | 5 / 11 | |
| 3.20.7 | 5 / 11 | |
| 3.20.6 | 5 / 11 | |
| 3.20.5 | 5 / 11 | |
| 3.20.3 | 5 / 11 | |
| 3.20.1 | 5 / 11 | |
| 3.19.2 | 5 / 11 | |
| 3.19.1 | 5 / 11 | |
| 3.19.0 | 5 / 11 | |
| 3.18.15 | 5 / 11 | |
| 3.18.13 | 5 / 11 | |
| 3.18.12 | 5 / 11 | |
| 3.18.11 | 5 / 11 |
v3.38.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.38.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.38.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.38.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.37.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.37.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.37.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.37.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.36.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.36.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.35.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.34.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.34.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.34.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.33.5
2 findingsThis version was published by a different npm account than previous versions on 2026-03-13. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.22.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.22.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.22.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.22.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.21.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.