@nocobase/plugin-block-workbench Apache-2.0 26 versions

@nocobase/plugin-block-workbench

npm

Centrally manages and displays various actions, allowing users to efficiently perform tasks. It supports extensibility, with current action types including pop-ups, links, scanning, and custom requests.

26

Versions

Apache-2.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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

chenosjiannlu

Keywords

Blocks

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:dist/client/403f3c00a8759a8e.js	AI (source-diff): Standard webpack-minified client bundle chunk with NocoBase copyright header. Minified JS is expected for this frontend plugin package across all versions.	ai	2026/04/27
source-diff	obfuscated-file:dist/client/397.f5856fbc9fcf5ec3.js	AI (source-diff): Standard webpack-bundled client JS with NocoBase copyright header and React component code. Minified build output is expected for this plugin package.	ai	2026/04/26
source-diff	encoded-string-file:dist/client/index.js	AI (source-diff): Long strings in index.js are CSS-in-JS content and UMD module wrappers — normal webpack build output for a React plugin, not obfuscated payloads.	ai	2026/04/26
source-diff	obfuscated-file:dist/client/54dcee37d9a65f71.js	AI (source-diff): Standard webpack-minified client bundle for a NocoBase frontend plugin. Content is readable QR scanner React component code, not malicious obfuscation.	ai	2026/04/26
source-diff	obfuscated-file:dist/client/d180e3dfa95b10ab.js	AI (source-diff): Standard webpack-minified bundle containing html5-qrcode library, matching the package's declared devDependency and QR scanning feature. Not malicious.	ai	2026/04/26
bogus-package	bogus-package	AI (bogus-package): NocoBase commercial plugins consistently lack public repo URLs and have sparse READMEs due to their dual-license model. 764 versions and 1.6k weekly downloads confirm legitimacy.	ai	2026/04/26

Versions (showing 26 of 126)

Version	Deps	Published
1.9.23	0 / 4	2025-12-09
1.9.22	0 / 4	2025-12-09
1.9.21	0 / 4	2025-12-06
1.9.20	0 / 4	2025-12-05
1.9.19	0 / 4	2025-12-04
1.9.18	0 / 4	2025-12-03
1.9.17	0 / 4	2025-12-02
1.9.16	0 / 4	2025-12-01
1.9.15	0 / 4	2025-11-28
1.9.14	0 / 4	2025-11-26
1.9.13	0 / 4	2025-11-25
1.9.12	0 / 4	2025-11-24
1.9.11	0 / 4	2025-11-21
1.9.10	0 / 4	2025-11-20
1.9.9	0 / 4	2025-11-19
1.9.8	0 / 4	2025-11-18
1.9.7	0 / 4	2025-11-17
1.9.6	0 / 4	2025-11-12
1.9.5	0 / 4	2025-11-10
1.9.4	0 / 4	2025-11-10
1.9.3	0 / 4	2025-11-05
1.9.2	0 / 4	2025-11-04
1.9.1	0 / 4	2025-11-04
1.9.0	0 / 4	2025-11-02
1.8.33	0 / 4	2025-10-29
1.8.32	0 / 4	2025-10-27

v1.9.23

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.22

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.21

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.20

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.19

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.18

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.17

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.8.33

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.

v1.8.32

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.