@nocobase/plugin-notifications
<video width="100%" controls> <source src="https://github.com/user-attachments/assets/4d11a87b-00e2-48f3-9bf7-389d21072d13" type="video/mp4"> </video>
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): @nocobase plugin packages are monorepo sub-packages with minimal standalone metadata by design; these signals are stable false positives for this package family. | ai |
Versions (showing 51 of 159)
| Version | Deps | Published |
|---|---|---|
| 2.1.31 | 0 / 3 | |
| 2.1.30 | 0 / 3 | |
| 2.1.29 | 0 / 3 | |
| 2.1.28 | 0 / 3 | |
| 2.1.27 | 0 / 3 | |
| 2.1.26 | 0 / 3 | |
| 2.1.25 | 0 / 3 | |
| 2.1.24 | 0 / 3 | |
| 2.1.23 | 0 / 3 | |
| 2.1.22 | 0 / 3 | |
| 2.1.21 | 0 / 3 | |
| 2.1.20 | 0 / 3 | |
| 2.1.19 | 0 / 3 | |
| 2.1.18 | 0 / 3 | |
| 2.1.17 | 0 / 3 | |
| 2.1.15 | 0 / 3 | |
| 2.1.14 | 0 / 3 | |
| 2.1.12 | 0 / 3 | |
| 2.1.11 | 0 / 3 | |
| 2.1.10 | 0 / 3 | |
| 2.1.9 | 0 / 3 | |
| 2.1.8 | 0 / 3 | |
| 2.1.7 | 0 / 3 | |
| 2.1.6 | 0 / 3 | |
| 2.1.5 | 0 / 3 | |
| 2.1.4 | 0 / 3 | |
| 2.1.3 | 0 / 3 | |
| 2.1.2 | 0 / 3 | |
| 2.1.1 | 0 / 3 | |
| 2.1.0 | 0 / 3 | |
| 2.0.62 | 0 / 3 | |
| 2.0.61 | 0 / 3 | |
| 2.0.60 | 0 / 3 | |
| 2.0.59 | 0 / 3 | |
| 2.0.58 | 0 / 3 | |
| 2.0.57 | 0 / 3 | |
| 2.0.56 | 0 / 3 | |
| 2.0.55 | 0 / 3 | |
| 2.0.54 | 0 / 3 | |
| 2.0.53 | 0 / 3 | |
| 2.0.52 | 0 / 3 | |
| 2.0.51 | 0 / 3 | |
| 2.0.50 | 0 / 3 | |
| 2.0.49 | 0 / 3 | |
| 2.0.48 | 0 / 3 | |
| 2.0.47 | 0 / 3 | |
| 2.0.46 | 0 / 3 | |
| 2.0.45 | 0 / 3 | |
| 2.0.44 | 0 / 3 | |
| 2.0.43 | 0 / 3 | |
| 2.0.42 | 0 / 3 |
v2.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.