@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 7 of 107)
| Version | Deps | Published |
|---|---|---|
| 3.11.1 | 5 / 14 | |
| 3.11.0 | 5 / 14 | |
| 3.10.7 | 5 / 14 | |
| 3.10.6 | 5 / 14 | |
| 3.10.2 | 5 / 14 | |
| 3.10.1 | 5 / 14 | |
| 3.10.0 | 5 / 14 |
v3.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.