@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 55 of 260)
| Version | Deps | Published |
|---|---|---|
| 3.13.21 | 17 / 13 | |
| 3.13.20 | 17 / 13 | |
| 3.13.19 | 17 / 13 | |
| 3.13.18 | 17 / 13 | |
| 3.13.17 | 17 / 13 | |
| 3.13.16 | 17 / 13 | |
| 3.13.15 | 17 / 13 | |
| 3.13.14 | 17 / 13 | |
| 3.13.13 | 17 / 13 | |
| 3.13.12 | 17 / 13 | |
| 3.13.11 | 17 / 13 | |
| 3.13.10 | 17 / 13 | |
| 3.13.9 | 17 / 13 | |
| 3.13.8 | 17 / 13 | |
| 3.13.7 | 17 / 13 | |
| 3.13.6 | 17 / 13 | |
| 3.13.5 | 17 / 13 | |
| 3.13.4 | 17 / 13 | |
| 3.13.3 | 17 / 13 | |
| 3.13.2 | 17 / 13 | |
| 3.13.1 | 17 / 13 | |
| 3.13.0 | 17 / 13 | |
| 3.12.21 | 17 / 13 | |
| 3.12.20 | 17 / 13 | |
| 3.12.19 | 17 / 13 | |
| 3.12.18 | 17 / 13 | |
| 3.12.17 | 17 / 13 | |
| 3.12.16 | 17 / 13 | |
| 3.12.15 | 17 / 13 | |
| 3.12.14 | 17 / 13 | |
| 3.12.13 | 17 / 13 | |
| 3.12.12 | 17 / 13 | |
| 3.12.11 | 17 / 13 | |
| 3.12.10 | 17 / 13 | |
| 3.12.9 | 17 / 13 | |
| 3.12.8 | 17 / 13 | |
| 3.12.7 | 17 / 13 | |
| 3.12.6 | 17 / 13 | |
| 3.12.5 | 17 / 13 | |
| 3.12.4 | 17 / 13 | |
| 3.12.3 | 17 / 13 | |
| 3.12.2 | 17 / 13 | |
| 3.12.1 | 17 / 13 | |
| 3.12.0 | 17 / 13 | |
| 3.11.2 | 17 / 13 | |
| 3.11.1 | 17 / 13 | |
| 3.11.0 | 17 / 13 | |
| 3.10.7 | 17 / 13 | |
| 3.10.6 | 17 / 13 | |
| 3.10.5 | 16 / 13 | |
| 3.10.4 | 16 / 13 | |
| 3.10.3 | 16 / 13 | |
| 3.10.2 | 16 / 13 | |
| 3.10.1 | 16 / 13 | |
| 3.10.0 | 16 / 13 |
v3.13.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.