← Home

@budibase/cli

npm

Budibase CLI, for developers, self hosting and migrations.

22
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

melbudibasepclmntjoranamochristos-budibase

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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
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
dependencies unvetted-dep:@budibase/types 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/string-templates AI (dependencies): First-party @budibase/* scoped package; stable 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/backend-core AI (dependencies): First-party @budibase/* scoped package; stable false positive. ai

Versions (showing 22 of 22)

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

v3.38.5

1 finding
LOW No provenance attestation provenance

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

v3.38.4

1 finding
LOW No provenance attestation provenance

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

v3.38.3

1 finding
LOW No provenance attestation provenance

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

v3.38.2

1 finding
LOW No provenance attestation provenance

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

v3.38.1

1 finding
LOW No provenance attestation provenance

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

v3.38.0

1 finding
LOW No provenance attestation provenance

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

v3.37.5

1 finding
LOW No provenance attestation provenance

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

v3.37.4

1 finding
LOW No provenance attestation provenance

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

v3.37.3

1 finding
LOW No provenance attestation provenance

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

v3.37.2

2 findings
HIGH Long encoded string in modified file: dist/index.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v3.37.0

1 finding
LOW No provenance attestation provenance

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

v3.36.5

1 finding
LOW No provenance attestation provenance

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

v3.36.4

1 finding
LOW No provenance attestation provenance

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

v3.36.3

1 finding
LOW No provenance attestation provenance

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

v3.36.2

1 finding
LOW No provenance attestation provenance

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

v3.36.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.

v3.35.10

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

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

v3.35.0

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.