@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 46 of 246)
| Version | Deps | Published |
|---|---|---|
| 3.13.12 | 41 / 23 | |
| 3.13.11 | 41 / 23 | |
| 3.13.10 | 40 / 23 | |
| 3.13.9 | 40 / 23 | |
| 3.13.8 | 40 / 23 | |
| 3.13.7 | 40 / 23 | |
| 3.13.6 | 40 / 23 | |
| 3.13.5 | 40 / 23 | |
| 3.13.4 | 40 / 23 | |
| 3.13.3 | 40 / 23 | |
| 3.13.2 | 40 / 23 | |
| 3.13.1 | 40 / 23 | |
| 3.13.0 | 40 / 23 | |
| 3.12.21 | 40 / 23 | |
| 3.12.20 | 40 / 23 | |
| 3.12.19 | 40 / 23 | |
| 3.12.18 | 40 / 23 | |
| 3.12.17 | 40 / 23 | |
| 3.12.16 | 40 / 23 | |
| 3.12.15 | 40 / 23 | |
| 3.12.14 | 40 / 23 | |
| 3.12.13 | 40 / 23 | |
| 3.12.12 | 40 / 23 | |
| 3.12.11 | 40 / 23 | |
| 3.12.10 | 40 / 23 | |
| 3.12.9 | 40 / 23 | |
| 3.12.8 | 40 / 23 | |
| 3.12.7 | 40 / 23 | |
| 3.12.6 | 40 / 24 | |
| 3.12.5 | 40 / 24 | |
| 3.12.4 | 40 / 24 | |
| 3.12.3 | 40 / 24 | |
| 3.12.2 | 40 / 24 | |
| 3.12.1 | 40 / 24 | |
| 3.12.0 | 40 / 24 | |
| 3.11.2 | 40 / 24 | |
| 3.11.1 | 39 / 23 | |
| 3.11.0 | 39 / 23 | |
| 3.10.7 | 39 / 23 | |
| 3.10.6 | 39 / 23 | |
| 3.10.5 | 39 / 23 | |
| 3.10.4 | 39 / 23 | |
| 3.10.3 | 39 / 23 | |
| 3.10.2 | 38 / 23 | |
| 3.10.1 | 38 / 23 | |
| 3.10.0 | 38 / 23 |
v3.13.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.13.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.13.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.13.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.13.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.13.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.13.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.13.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.13.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.13.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.13.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.13.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.13.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.12.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.12.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.12.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.12.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.12.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.12.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.12.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.12.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.12.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.12.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.12.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.12.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.12.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.12.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.12.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.12.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.12.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.12.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.12.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.12.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.12.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.12.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.11.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.11.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.11.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.10.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.10.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.10.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.10.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.10.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.10.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.10.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.10.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.