@budibase/frontend-core
Budibase frontend core libraries used in builder and client
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Budibase internal team rotation; new maintainers are known Budibase contributors. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): shogunpurple removal consistent with Budibase team transition, not a hostile takeover. | ai | |
| phantom-deps | phantom-dep:shortid | AI (phantom-deps): shortid is a declared runtime dep in package.json; phantom-dep false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Budibase monorepo packages consistently lack provenance attestation; stable false positive for this publisher. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/svelte | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic false positive for this package. | ai | |
| dependencies | unvetted-dep:@budibase/bbui | AI (dependencies): Internal Budibase monorepo sibling dep; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Missing repo/keywords is consistent with monorepo publishing; not a spam package. | ai | |
| dependencies | unvetted-dep:@budibase/types | AI (dependencies): Internal Budibase monorepo sibling dep; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@budibase/shared-core | AI (dependencies): Internal Budibase monorepo sibling dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:dayjs | AI (phantom-deps): dayjs is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 51 of 187)
| Version | Deps | Published |
|---|---|---|
| 3.38.5 | 8 / 1 | |
| 3.38.4 | 8 / 1 | |
| 3.38.3 | 8 / 1 | |
| 3.38.2 | 8 / 1 | |
| 3.38.1 | 8 / 1 | |
| 3.38.0 | 8 / 1 | |
| 3.37.5 | 8 / 1 | |
| 3.37.4 | 8 / 1 | |
| 3.37.3 | 8 / 1 | |
| 3.37.2 | 8 / 1 | |
| 3.37.1 | 8 / 1 | |
| 3.37.0 | 8 / 1 | |
| 3.36.5 | 8 / 1 | |
| 3.36.4 | 8 / 1 | |
| 3.36.3 | 8 / 1 | |
| 3.36.2 | 8 / 1 | |
| 3.36.1 | 8 / 1 | |
| 3.35.10 | 8 / 1 | |
| 3.35.3 | 8 / 1 | |
| 3.35.2 | 8 / 1 | |
| 3.35.1 | 8 / 1 | |
| 3.35.0 | 8 / 1 | |
| 3.34.6 | 8 / 1 | |
| 3.33.1 | 9 / 1 | |
| 3.31.6 | 9 / 1 | |
| 3.24.4 | 8 / 0 | |
| 3.23.47 | 8 / 0 | |
| 3.23.38 | 8 / 0 | |
| 3.23.37 | 8 / 0 | |
| 3.23.36 | 8 / 0 | |
| 3.23.35 | 8 / 0 | |
| 3.23.34 | 8 / 0 | |
| 3.23.33 | 8 / 0 | |
| 3.23.32 | 8 / 0 | |
| 3.23.31 | 8 / 0 | |
| 3.23.30 | 8 / 0 | |
| 3.23.29 | 8 / 0 | |
| 3.23.28 | 8 / 0 | |
| 3.23.27 | 8 / 0 | |
| 3.23.26 | 7 / 0 | |
| 3.23.25 | 7 / 0 | |
| 3.23.24 | 7 / 0 | |
| 3.23.23 | 7 / 0 | |
| 3.23.22 | 7 / 0 | |
| 3.23.20 | 7 / 0 | |
| 3.23.19 | 7 / 0 | |
| 3.23.18 | 7 / 0 | |
| 3.23.17 | 7 / 0 | |
| 3.23.16 | 7 / 0 | |
| 3.23.15 | 7 / 0 | |
| 3.23.14 | 7 / 0 |
v3.38.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.38.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.38.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.38.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.38.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.38.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.37.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.37.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.37.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.37.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.37.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.36.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.36.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.36.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.36.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.35.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.35.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.35.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.34.6
2 findingsThis version was published by a different npm account than previous versions on 2026-03-23. 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.
v3.33.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-11. 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.
v3.31.6
2 findingsThis version was published by a different npm account than previous versions on 2026-03-05. 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.
v3.24.4
2 findingsThis version was published by a different npm account than previous versions on 2026-01-16. 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.
v3.23.47
2 findingsThis version was published by a different npm account than previous versions on 2026-01-05. 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.
v3.23.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.