@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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Old maintainers replaced by current Budibase org members. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change is part of Budibase org maintainer consolidation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by org-level maintainer transition on a scoped fork. | 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 |
v0.14.3
3 findingsAll previous maintainers (shogunpurple, mike_chuckles) were replaced by new maintainers (melbudibase, pclmnt, joranamo, christos-budibase). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2026-05-25. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.