@budibase/worker
Budibase background service
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@govtechsg/passport-openidconnect | AI (dependencies): GovTech SG OIDC passport strategy replacing @techpass/passport-openidconnect; routine upstream rename. | ai | |
| phantom-deps | phantom-dep:@govtechsg/passport-openidconnect | AI (phantom-deps): Bundled service; config-file reference pattern is expected. | ai | |
| dependencies | unvetted-dep:passport-google-oauth | AI (dependencies): Well-known Passport.js OAuth strategy; expected auth dependency for this package. | ai | |
| dependencies | unvetted-dep:pouchdb-all-dbs | AI (dependencies): Standard PouchDB plugin used in Budibase's DB layer; consistent across versions. | ai | |
| dependencies | unvetted-dep:@techpass/passport-openidconnect | AI (dependencies): OIDC passport strategy used for SSO; consistent with Budibase's auth features. | ai | |
| phantom-deps | phantom-dep:undici | AI (phantom-deps): Monorepo bundled package; phantom-dep heuristic unreliable for bundled outputs. | ai | |
| phantom-deps | phantom-dep:aws-sdk | AI (phantom-deps): Config-referenced; expected in Budibase worker for cloud integrations. | ai | |
| phantom-deps | phantom-dep:bcryptjs | AI (phantom-deps): Auth utility; config-referenced in monorepo build. | ai | |
| phantom-deps | phantom-dep:koa-send | AI (phantom-deps): Koa middleware; config-referenced in monorepo build. | ai | |
| phantom-deps | phantom-dep:koa-static | AI (phantom-deps): Koa middleware; config-referenced in monorepo build. | ai | |
| phantom-deps | phantom-dep:koa-passport | AI (phantom-deps): Koa auth middleware; config-referenced in monorepo build. | ai | |
| phantom-deps | phantom-dep:passport-local | AI (phantom-deps): Passport strategy; config-referenced in monorepo build. | ai | |
| phantom-deps | phantom-dep:server-destroy | AI (phantom-deps): Server utility; config-referenced in monorepo build. | ai | |
| phantom-deps | phantom-dep:pouchdb-all-dbs | AI (phantom-deps): PouchDB plugin; config-referenced in monorepo build. | ai | |
| phantom-deps | phantom-dep:passport-google-oauth | AI (phantom-deps): Passport strategy; config-referenced in monorepo build. | ai | |
| phantom-deps | phantom-dep:@techpass/passport-openidconnect | AI (phantom-deps): OIDC strategy; config-referenced in monorepo build. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Active Budibase monorepo package with 3070+ versions; dormancy flag is a false positive for this high-frequency publisher. | ai | |
| dependencies | unvetted-dep:scim2-parse-filter | AI (dependencies): Long-standing dep in this package; no advisory; stable across versions. | ai | |
| dependencies | unvetted-dep:scim-patch | AI (dependencies): Long-standing dep in this package; no advisory; stable across versions. | ai | |
| dependencies | unvetted-dep:@types/global-agent | AI (dependencies): Type-only dev-adjacent dep; no risk; stable across versions. | ai | |
| dependencies | unvetted-dep:bull | AI (dependencies): Long-standing dep in this package; no advisory; stable across versions. | ai | |
| dependencies | unvetted-dep:koa-redis | AI (dependencies): Long-standing dep in this package; no advisory; stable across versions. | ai | |
| license | copyleft-license:GPL-3.0 | AI (license): GPL-3.0 is the intentional license for the Budibase project. | ai | |
| provenance | no-provenance | AI (provenance): Budibase monorepo does not publish Sigstore provenance; consistent across all versions. | ai | |
| phantom-deps | phantom-dep:bull | AI (phantom-deps): Referenced in config files per phantom-dep finding; consistent with queue worker pattern in this monorepo. | ai | |
| phantom-deps | phantom-dep:pouchdb | AI (phantom-deps): Config-file reference; consistent with Budibase's CouchDB/PouchDB usage. | ai | |
| phantom-deps | phantom-dep:isolated-vm | AI (phantom-deps): Config-file reference; expected for sandboxed JS execution in worker. | ai | |
| phantom-deps | phantom-dep:@types/global-agent | AI (phantom-deps): Framework-scoped types package; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:knex | AI (phantom-deps): Config-file reference only; standard DB dependency pattern for this package. | ai | |
| phantom-deps | phantom-dep:bcrypt | AI (phantom-deps): Config-file reference; expected for auth/worker service. | ai |
Versions (showing 100 of 246)
| Version | Deps | Published |
|---|---|---|
| 3.23.24 | 42 / 17 | |
| 3.23.23 | 42 / 17 | |
| 3.23.22 | 42 / 17 | |
| 3.23.20 | 42 / 17 | |
| 3.23.19 | 42 / 17 | |
| 3.23.18 | 42 / 17 | |
| 3.23.17 | 42 / 17 | |
| 3.23.16 | 42 / 17 | |
| 3.23.15 | 42 / 17 | |
| 3.23.14 | 42 / 17 | |
| 3.23.13 | 42 / 17 | |
| 3.23.12 | 42 / 17 | |
| 3.23.11 | 42 / 17 | |
| 3.23.10 | 42 / 17 | |
| 3.23.9 | 42 / 17 | |
| 3.23.8 | 42 / 17 | |
| 3.23.7 | 42 / 17 | |
| 3.23.6 | 42 / 17 | |
| 3.23.5 | 42 / 17 | |
| 3.23.4 | 42 / 17 | |
| 3.23.3 | 42 / 17 | |
| 3.23.2 | 42 / 17 | |
| 3.23.1 | 42 / 17 | |
| 3.23.0 | 42 / 18 | |
| 3.22.7 | 42 / 18 | |
| 3.22.6 | 42 / 18 | |
| 3.22.5 | 42 / 18 | |
| 3.22.4 | 42 / 18 | |
| 3.22.3 | 42 / 18 | |
| 3.22.2 | 42 / 18 | |
| 3.22.1 | 42 / 18 | |
| 3.22.0 | 42 / 18 | |
| 3.21.3 | 42 / 18 | |
| 3.21.2 | 42 / 18 | |
| 3.21.1 | 42 / 18 | |
| 3.21.0 | 42 / 18 | |
| 3.20.15 | 42 / 18 | |
| 3.20.14 | 42 / 18 | |
| 3.20.13 | 42 / 18 | |
| 3.20.12 | 41 / 18 | |
| 3.20.11 | 41 / 18 | |
| 3.20.10 | 41 / 18 | |
| 3.20.9 | 41 / 18 | |
| 3.20.8 | 41 / 18 | |
| 3.20.7 | 41 / 18 | |
| 3.20.6 | 41 / 18 | |
| 3.20.5 | 41 / 18 | |
| 3.20.4 | 41 / 18 | |
| 3.20.3 | 41 / 18 | |
| 3.20.2 | 41 / 18 | |
| 3.20.1 | 41 / 18 | |
| 3.20.0 | 41 / 18 | |
| 3.19.2 | 41 / 18 | |
| 3.19.1 | 41 / 18 | |
| 3.19.0 | 41 / 18 | |
| 3.18.15 | 41 / 18 | |
| 3.18.14 | 41 / 18 | |
| 3.18.13 | 41 / 18 | |
| 3.18.12 | 41 / 18 | |
| 3.18.11 | 41 / 18 | |
| 3.18.10 | 41 / 18 | |
| 3.18.9 | 41 / 18 | |
| 3.18.8 | 41 / 18 | |
| 3.18.7 | 41 / 18 | |
| 3.18.6 | 41 / 18 | |
| 3.18.5 | 41 / 18 | |
| 3.18.4 | 41 / 18 | |
| 3.18.3 | 41 / 18 | |
| 3.18.2 | 41 / 18 | |
| 3.18.1 | 41 / 18 | |
| 3.18.0 | 41 / 23 | |
| 3.17.5 | 41 / 24 | |
| 3.17.4 | 41 / 24 | |
| 3.17.3 | 41 / 24 | |
| 3.17.2 | 41 / 24 | |
| 3.17.1 | 41 / 24 | |
| 3.17.0 | 41 / 24 | |
| 3.16.1 | 41 / 24 | |
| 3.16.0 | 41 / 24 | |
| 3.15.1 | 41 / 24 | |
| 3.15.0 | 41 / 24 | |
| 3.14.1 | 41 / 24 | |
| 3.14.0 | 41 / 24 | |
| 3.13.29 | 41 / 23 | |
| 3.13.28 | 41 / 23 | |
| 3.13.27 | 41 / 23 | |
| 3.13.26 | 41 / 23 | |
| 3.13.25 | 41 / 23 | |
| 3.13.24 | 41 / 23 | |
| 3.13.23 | 41 / 23 | |
| 3.13.22 | 41 / 23 | |
| 3.13.21 | 41 / 23 | |
| 3.13.20 | 41 / 23 | |
| 3.13.19 | 41 / 23 | |
| 3.13.18 | 41 / 23 | |
| 3.13.17 | 41 / 23 | |
| 3.13.16 | 41 / 23 | |
| 3.13.15 | 41 / 23 | |
| 3.13.14 | 41 / 23 | |
| 3.13.13 | 41 / 23 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.23.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.
v3.23.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.23.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.23.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.23.2
1 finding[Accepted risk] 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[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.21.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.21.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.