← Home

@budibase/cli

npm

Budibase CLI, for developers, self hosting and migrations.

61
Versions
GPL-3.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

melbudibasepclmntjoranamochristos-budibase

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Budibase org maintainer rotation; publisher has strong vetted track record. ai
maintainer-change maintainer-removed AI (maintainer-change): Part of same legitimate maintainer rotation. ai
source-diff encoded-string-file:dist/index.js AI (source-diff): Encoded strings are ANSI terminal escape sequences for CLI banner rendering, not obfuscated payloads. ai
dependencies unvetted-dep:@budibase/types AI (dependencies): First-party @budibase/* scoped package; stable false positive. ai
dependencies unvetted-dep:@budibase/backend-core AI (dependencies): First-party @budibase/* scoped package; stable false positive. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped @budibase/cli package; levenshtein match to 'joi' is a false positive. ai
dependencies unvetted-dep:@budibase/pouchdb-replication-stream AI (dependencies): First-party @budibase/* scoped package; stable false positive. ai
dependencies unvetted-dep:@budibase/string-templates AI (dependencies): First-party @budibase/* scoped package; stable false positive. ai
semgrep semgrep:child-process-import AI (semgrep): CLI tool legitimately uses child_process for system command execution. ai
semgrep semgrep:shady-links-raw-ip AI (semgrep): 169.254.169.254 is the standard cloud instance metadata endpoint used for DO/AWS init config. ai

Versions (showing 61 of 61)

Version Deps Published
3.38.5 20 / 3
3.38.4 20 / 3
3.38.3 20 / 3
3.38.2 20 / 3
3.38.1 20 / 3
3.38.0 20 / 3
3.37.5 20 / 3
3.37.4 20 / 3
3.37.3 20 / 3
3.37.2 20 / 3
3.37.1 20 / 3
3.37.0 20 / 3
3.36.5 20 / 3
3.36.4 20 / 3
3.36.3 20 / 3
3.36.2 20 / 3
3.36.1 20 / 3
3.35.10 20 / 3
3.35.3 20 / 3
3.35.2 20 / 3
3.35.1 20 / 3
3.35.0 20 / 3
3.24.6 20 / 3
3.23.47 20 / 3
3.23.38 20 / 3
3.23.37 20 / 3
3.23.36 20 / 3
3.23.35 20 / 3
3.23.34 20 / 3
3.23.33 20 / 3
3.23.32 20 / 3
3.23.31 20 / 3
3.23.30 20 / 3
3.23.29 20 / 3
3.23.28 20 / 3
3.23.27 20 / 3
3.23.26 20 / 3
3.23.25 20 / 3
3.23.24 20 / 3
3.23.23 20 / 3
3.23.22 20 / 3
3.23.20 20 / 3
3.23.19 20 / 3
3.23.18 20 / 3
3.23.17 20 / 3
3.23.16 20 / 3
3.23.15 20 / 3
3.23.14 20 / 3
3.23.13 20 / 3
3.23.12 20 / 3
3.23.11 20 / 3
3.23.10 20 / 3
3.23.9 20 / 3
3.23.8 20 / 3
3.23.7 20 / 3
3.23.6 20 / 3
3.23.5 20 / 3
3.23.4 20 / 3
3.23.3 20 / 3
3.23.2 20 / 3
3.23.1 20 / 3

v3.24.6

2 findings
HIGH Publisher changed: shogunpurple → christos-budibase (on 2026-01-21) provenance

This version was published by a different npm account than previous versions on 2026-01-21. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.47

2 findings
HIGH Publisher changed: shogunpurple → christos-budibase (on 2026-01-05) provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.38

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.37

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.36

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.35

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.34

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.33

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.32

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.31

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.30

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.29

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.28

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.27

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.26

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.25

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.24

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.23

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.22

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.20

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.19

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.18

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.17

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.16

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.15

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.23.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.23.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.