@budibase/pro
Budibase Pro (Backend)
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): christos-budibase is an established Budibase org publisher with strong track record; transition appears legitimate. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): shogunpurple removal is consistent with internal team transition at Budibase. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): christos-budibase is an established Budibase org publisher; team rotation within same org. | ai | |
| phantom-deps | phantom-dep:@ai-sdk/openai | AI (phantom-deps): Newly added AI SDK dep; referenced in config/re-exported rather than directly imported. | ai | |
| phantom-deps | phantom-dep:ai | AI (phantom-deps): ai is a declared runtime dep likely re-exported; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:undici | AI (phantom-deps): undici is declared as a direct dependency in package.json; phantom-dep false positive. | ai | |
| dependencies | unvetted-dep:bull | AI (dependencies): bull is a well-known Redis-based job queue; stable dependency for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Private/proprietary Budibase monorepo package; sparse README and no keywords are expected. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): High-frequency Budibase monorepo package with 2265 versions; dormancy signal is a false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @budibase/pro cannot be a typosquat of 'pg'; Levenshtein match is spurious. | ai | |
| phantom-deps | phantom-dep:bull | AI (phantom-deps): bull is a declared runtime dep used in config/queue setup; phantom-dep heuristic fires on indirect usage patterns. | ai | |
| typosquat | typosquat.levenshtein:pino | AI (typosquat): Scoped package @budibase/pro cannot be a typosquat of 'pino'; Levenshtein match is spurious. | ai |
Versions (showing 100 of 260)
| Version | Deps | Published |
|---|---|---|
| 3.23.33 | 20 / 9 | |
| 3.23.32 | 20 / 9 | |
| 3.23.31 | 20 / 9 | |
| 3.23.30 | 20 / 9 | |
| 3.23.29 | 20 / 9 | |
| 3.23.28 | 20 / 9 | |
| 3.23.27 | 20 / 9 | |
| 3.23.26 | 18 / 9 | |
| 3.23.25 | 18 / 9 | |
| 3.23.24 | 18 / 9 | |
| 3.23.23 | 18 / 9 | |
| 3.23.22 | 18 / 9 | |
| 3.23.20 | 18 / 9 | |
| 3.23.19 | 18 / 9 | |
| 3.23.18 | 18 / 9 | |
| 3.23.17 | 18 / 9 | |
| 3.23.16 | 18 / 9 | |
| 3.23.15 | 18 / 9 | |
| 3.23.14 | 18 / 9 | |
| 3.23.13 | 18 / 9 | |
| 3.23.12 | 18 / 9 | |
| 3.23.11 | 18 / 9 | |
| 3.23.10 | 18 / 9 | |
| 3.23.9 | 18 / 9 | |
| 3.23.8 | 18 / 9 | |
| 3.23.7 | 18 / 9 | |
| 3.23.6 | 18 / 9 | |
| 3.23.5 | 18 / 9 | |
| 3.23.4 | 18 / 9 | |
| 3.23.3 | 18 / 9 | |
| 3.23.2 | 18 / 9 | |
| 3.23.1 | 18 / 9 | |
| 3.23.0 | 18 / 9 | |
| 3.22.7 | 18 / 9 | |
| 3.22.6 | 18 / 9 | |
| 3.22.5 | 18 / 9 | |
| 3.22.4 | 18 / 9 | |
| 3.22.3 | 18 / 9 | |
| 3.22.2 | 18 / 9 | |
| 3.22.1 | 18 / 9 | |
| 3.22.0 | 18 / 9 | |
| 3.21.3 | 18 / 9 | |
| 3.21.2 | 17 / 9 | |
| 3.21.1 | 17 / 9 | |
| 3.21.0 | 17 / 9 | |
| 3.20.15 | 17 / 9 | |
| 3.20.14 | 17 / 9 | |
| 3.20.13 | 17 / 9 | |
| 3.20.12 | 17 / 9 | |
| 3.20.11 | 17 / 9 | |
| 3.20.10 | 17 / 9 | |
| 3.20.9 | 17 / 9 | |
| 3.20.8 | 17 / 9 | |
| 3.20.7 | 17 / 9 | |
| 3.20.6 | 17 / 9 | |
| 3.20.5 | 17 / 9 | |
| 3.20.4 | 17 / 9 | |
| 3.20.3 | 17 / 9 | |
| 3.20.2 | 17 / 9 | |
| 3.20.1 | 17 / 9 | |
| 3.20.0 | 17 / 9 | |
| 3.19.2 | 17 / 9 | |
| 3.19.1 | 17 / 9 | |
| 3.19.0 | 17 / 9 | |
| 3.18.15 | 17 / 9 | |
| 3.18.14 | 17 / 9 | |
| 3.18.13 | 17 / 9 | |
| 3.18.12 | 17 / 9 | |
| 3.18.11 | 17 / 9 | |
| 3.18.10 | 17 / 9 | |
| 3.18.9 | 17 / 9 | |
| 3.18.8 | 17 / 9 | |
| 3.18.7 | 17 / 9 | |
| 3.18.6 | 17 / 9 | |
| 3.18.5 | 17 / 9 | |
| 3.18.4 | 17 / 9 | |
| 3.18.3 | 17 / 9 | |
| 3.18.2 | 17 / 9 | |
| 3.18.1 | 17 / 9 | |
| 3.18.0 | 17 / 12 | |
| 3.17.5 | 17 / 13 | |
| 3.17.4 | 17 / 13 | |
| 3.17.3 | 17 / 13 | |
| 3.17.2 | 17 / 13 | |
| 3.17.1 | 17 / 13 | |
| 3.17.0 | 17 / 13 | |
| 3.16.1 | 17 / 13 | |
| 3.16.0 | 17 / 13 | |
| 3.15.1 | 17 / 13 | |
| 3.15.0 | 17 / 13 | |
| 3.14.1 | 17 / 13 | |
| 3.14.0 | 17 / 13 | |
| 3.13.29 | 17 / 13 | |
| 3.13.28 | 17 / 13 | |
| 3.13.27 | 17 / 13 | |
| 3.13.26 | 17 / 13 | |
| 3.13.25 | 17 / 13 | |
| 3.13.24 | 17 / 13 | |
| 3.13.23 | 17 / 13 | |
| 3.13.22 | 17 / 13 |
v3.23.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.23.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.21.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.