← Home

@budibase/shared-core

npm

Shared data utils

100
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

melbudibasepclmntjoranamochristos-budibase

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Budibase org internal publisher rotation; new publisher is a Budibase team member with no malicious indicators. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers are Budibase org members; consistent with team growth/rotation on an established package. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of shogunpurple consistent with internal Budibase team transition, not a hostile takeover. ai
dependencies unvetted-dep:@budibase/types AI (dependencies): Internal monorepo sibling dependency; wildcard version is standard Budibase monorepo practice. ai

Versions (showing 100 of 381)

Version Deps Published
3.17.5 2 / 2
3.17.4 2 / 2
3.17.3 2 / 2
3.17.2 2 / 2
3.17.1 2 / 2
3.17.0 2 / 2
3.16.1 2 / 2
3.16.0 2 / 2
3.15.1 2 / 2
3.15.0 2 / 2
3.14.1 2 / 2
3.14.0 2 / 2
3.13.29 2 / 2
3.13.28 2 / 2
3.13.27 2 / 2
3.13.26 2 / 2
3.13.25 2 / 2
3.13.24 2 / 2
3.13.23 2 / 2
3.13.22 2 / 2
3.13.21 2 / 2
3.13.20 2 / 2
3.13.19 2 / 2
3.13.18 2 / 2
3.13.17 2 / 2
3.13.16 2 / 2
3.13.15 2 / 2
3.13.14 2 / 2
3.13.13 2 / 2
3.13.12 2 / 2
3.13.11 2 / 2
3.13.10 2 / 2
3.13.9 2 / 2
3.13.8 2 / 2
3.13.7 2 / 2
3.13.6 2 / 2
3.13.5 2 / 2
3.13.4 2 / 2
3.13.3 2 / 2
3.13.2 2 / 2
3.13.1 2 / 2
3.13.0 2 / 2
3.12.21 2 / 2
3.12.20 2 / 2
3.12.19 2 / 2
3.12.18 2 / 2
3.12.17 2 / 2
3.12.16 2 / 2
3.12.15 2 / 2
3.12.14 2 / 2
3.12.13 2 / 2
3.12.12 2 / 2
3.12.11 2 / 2
3.12.10 2 / 2
3.12.9 2 / 2
3.12.8 2 / 2
3.12.7 2 / 2
3.12.6 2 / 2
3.12.5 2 / 2
3.12.4 2 / 2
3.12.3 2 / 2
3.12.2 2 / 2
3.12.1 2 / 2
3.12.0 2 / 2
3.11.2 2 / 2
3.11.1 2 / 2
3.11.0 2 / 2
3.10.7 2 / 2
3.10.6 2 / 2
3.10.5 2 / 2
3.10.4 2 / 2
3.10.3 2 / 2
3.10.2 2 / 2
3.10.1 2 / 2
3.10.0 2 / 2
3.9.5 2 / 2
3.9.4 2 / 2
3.9.3 2 / 2
3.9.2 2 / 2
3.9.1 2 / 2
3.9.0 2 / 2
3.8.6 2 / 2
3.8.5 2 / 2
3.8.4 2 / 2
3.8.3 2 / 2
3.8.2 2 / 2
3.8.1 2 / 2
3.8.0 2 / 2
3.7.5 2 / 2
3.7.4 2 / 2
3.7.3 2 / 2
3.7.2 2 / 2
3.7.1 2 / 2
3.7.0 2 / 2
3.6.0 2 / 2
3.5.3 2 / 2
3.5.2 2 / 2
3.5.1 2 / 2
3.5.0 2 / 2
3.4.24 2 / 2
Showing 100 of 381 Next page →

v3.9.5

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

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

v3.8.6

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

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

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

v3.7.5

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

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

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

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

v3.4.24

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.