← Home

@nocobase/plugin-mock-collections

<video width="100%" controls> <source src="https://github.com/user-attachments/assets/4d11a87b-00e2-48f3-9bf7-389d21072d13" type="video/mp4"> </video>

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

Maintainers

chenosjiannlu

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): @nocobase plugins consistently lack repo URLs, keywords, and detailed READMEs — this is an org-wide convention, not spam. Package is legitimate with 845 versions and 895 days of history. ai
provenance no-provenance AI (provenance): NocoBase publishes hundreds of plugins without Sigstore provenance; publisher has 1176 approved packages with no rejections — stable false positive for this package family. ai

Versions (showing 51 of 159)

View all versions
Version Deps Published
2.1.31 0 / 1
2.1.30 0 / 1
2.1.29 0 / 1
2.1.28 0 / 1
2.1.27 0 / 1
2.1.26 0 / 1
2.1.25 0 / 1
2.1.24 0 / 1
2.1.23 0 / 1
2.1.22 0 / 1
2.1.21 0 / 1
2.1.20 0 / 1
2.1.19 0 / 1
2.1.18 0 / 1
2.1.17 0 / 1
2.1.15 0 / 1
2.1.14 0 / 1
2.1.12 0 / 1
2.1.11 0 / 1
2.1.10 0 / 1
2.1.9 0 / 1
2.1.8 0 / 1
2.1.7 0 / 1
2.1.6 0 / 1
2.1.5 0 / 1
2.1.4 0 / 1
2.1.3 0 / 1
2.1.2 0 / 1
2.1.1 0 / 1
2.1.0 0 / 1
2.0.62 0 / 1
2.0.61 0 / 1
2.0.60 0 / 1
2.0.59 0 / 1
2.0.58 0 / 1
2.0.57 0 / 1
2.0.56 0 / 1
2.0.55 0 / 1
2.0.54 0 / 1
2.0.53 0 / 1
2.0.52 0 / 1
2.0.51 0 / 1
2.0.50 0 / 1
2.0.49 0 / 1
2.0.48 0 / 1
2.0.47 0 / 1
2.0.46 0 / 1
2.0.45 0 / 1
2.0.44 0 / 1
2.0.43 0 / 1
2.0.42 0 / 1

v2.1.31

1 finding
INFO No provenance attestation provenance

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

v2.1.30

1 finding
INFO No provenance attestation provenance

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

v2.1.29

1 finding
INFO No provenance attestation provenance

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

v2.1.28

1 finding
INFO No provenance attestation provenance

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

v2.1.27

1 finding
INFO No provenance attestation provenance

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

v2.1.26

1 finding
INFO No provenance attestation provenance

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

v2.1.25

1 finding
INFO No provenance attestation provenance

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

v2.1.24

1 finding
INFO No provenance attestation provenance

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

v2.1.23

1 finding
INFO No provenance attestation provenance

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

v2.1.22

1 finding
INFO No provenance attestation provenance

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

v2.1.21

1 finding
INFO No provenance attestation provenance

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

v2.1.20

1 finding
INFO No provenance attestation provenance

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

v2.1.19

1 finding
INFO No provenance attestation provenance

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

v2.1.18

1 finding
INFO No provenance attestation provenance

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

v2.1.17

1 finding
INFO No provenance attestation provenance

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

v2.1.15

1 finding
INFO No provenance attestation provenance

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

v2.1.14

1 finding
INFO No provenance attestation provenance

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