@budibase/handlebars-helpers
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Publish-env metadata change only; no code-level malicious signal. | ai | |
| phantom-deps | phantom-dep:for-own | AI (phantom-deps): Small utility dep used internally in lib helpers; no malicious install behavior. | ai | |
| phantom-deps | phantom-dep:arr-flatten | AI (phantom-deps): Small utility dep used internally in lib helpers; no malicious install behavior. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Old maintainers replaced by current Budibase org members. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by org-level maintainer transition on a scoped fork. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change is part of Budibase org maintainer consolidation. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): Budibase org consolidating maintainers on their own scoped fork; all new names contain 'budibase'. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are Budibase org members; legitimate transfer. | ai | |
| provenance | no-provenance | AI (provenance): Budibase packages consistently lack Sigstore provenance; this is a stable characteristic of the publisher, not a security concern. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.14.3 | 13 / 19 | |
| 0.14.2 | 13 / 19 | |
| 0.14.1 | 12 / 19 | |
| 0.14.0 | 13 / 19 | |
| 0.13.2 | 13 / 19 | |
| 0.13.1 | 13 / 19 | |
| 0.13.0 | 13 / 19 | |
| 0.12.2 | 13 / 19 | |
| 0.12.1 | 12 / 19 | |
| 0.12.0 | 13 / 19 | |
| 0.11.11 | 17 / 20 | |
| 0.11.10 | 17 / 20 | |
| 0.11.9 | 16 / 20 | |
| 0.11.8 | 19 / 20 | |
| 0.11.7 | 21 / 20 | |
| 0.11.6 | 22 / 20 | |
| 0.11.5 | 22 / 20 | |
| 0.11.4 | 26 / 20 | |
| 0.11.3 | 26 / 20 | |
| 0.11.2 | 26 / 20 | |
| 0.11.1 | 26 / 20 | |
| 0.11.0 | 27 / 20 |
v0.14.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mike_chuckles) than the most recent previously approved version (shogunpurple) on 2025-03-11, but mike_chuckles is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.11
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: mike_chuckles.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.10
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: mike_chuckles.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.