@nocobase/plugin-charts
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
Versions (showing 100 of 131)
| Version | Deps | Published |
|---|---|---|
| 1.9.63 | 0 / 10 | |
| 1.9.62 | 0 / 10 | |
| 1.9.61 | 0 / 10 | |
| 1.9.60 | 0 / 10 | |
| 1.9.59 | 0 / 10 | |
| 1.9.58 | 0 / 10 | |
| 1.9.57 | 0 / 10 | |
| 1.9.56 | 0 / 10 | |
| 1.9.55 | 0 / 10 | |
| 1.9.54 | 0 / 10 | |
| 1.9.53 | 0 / 10 | |
| 1.9.52 | 0 / 10 | |
| 1.9.51 | 0 / 10 | |
| 1.9.49 | 0 / 10 | |
| 1.9.47 | 0 / 10 | |
| 1.9.46 | 0 / 10 | |
| 1.9.45 | 0 / 10 | |
| 1.9.44 | 0 / 10 | |
| 1.9.43 | 0 / 10 | |
| 1.9.42 | 0 / 10 | |
| 1.9.41 | 0 / 10 | |
| 1.9.40 | 0 / 10 | |
| 1.9.39 | 0 / 10 | |
| 1.9.38 | 0 / 10 | |
| 1.9.37 | 0 / 10 | |
| 1.9.36 | 0 / 10 | |
| 1.9.35 | 0 / 10 | |
| 1.9.34 | 0 / 10 | |
| 1.9.33 | 0 / 10 | |
| 1.9.32 | 0 / 10 | |
| 1.9.31 | 0 / 10 | |
| 1.9.30 | 0 / 10 | |
| 1.9.29 | 0 / 10 | |
| 1.9.28 | 0 / 10 | |
| 1.9.27 | 0 / 10 | |
| 1.9.26 | 0 / 10 | |
| 1.9.25 | 0 / 10 | |
| 1.9.24 | 0 / 10 | |
| 1.9.23 | 0 / 10 | |
| 1.9.22 | 0 / 10 | |
| 1.9.21 | 0 / 10 | |
| 1.9.20 | 0 / 10 | |
| 1.9.19 | 0 / 10 | |
| 1.9.18 | 0 / 10 | |
| 1.9.17 | 0 / 10 | |
| 1.9.16 | 0 / 10 | |
| 1.9.15 | 0 / 10 | |
| 1.9.14 | 0 / 10 | |
| 1.9.13 | 0 / 10 | |
| 1.9.12 | 0 / 10 | |
| 1.9.11 | 0 / 10 | |
| 1.9.10 | 0 / 10 | |
| 1.9.9 | 0 / 10 | |
| 1.9.8 | 0 / 10 | |
| 1.9.7 | 0 / 10 | |
| 1.9.6 | 0 / 10 | |
| 1.9.5 | 0 / 10 | |
| 1.9.4 | 0 / 10 | |
| 1.9.3 | 0 / 10 | |
| 1.9.2 | 0 / 10 | |
| 1.9.1 | 0 / 10 | |
| 1.9.0 | 0 / 10 | |
| 1.8.33 | 0 / 10 | |
| 1.8.32 | 0 / 10 | |
| 1.8.31 | 0 / 10 | |
| 1.8.30 | 0 / 10 | |
| 1.8.29 | 0 / 10 | |
| 1.8.28 | 0 / 10 | |
| 1.8.27 | 0 / 10 | |
| 1.8.26 | 0 / 10 | |
| 1.8.25 | 0 / 10 | |
| 1.8.24 | 0 / 10 | |
| 1.8.23 | 0 / 10 | |
| 1.8.22 | 0 / 10 | |
| 1.8.21 | 0 / 10 | |
| 1.8.20 | 0 / 10 | |
| 1.8.19 | 0 / 10 | |
| 1.8.18 | 0 / 10 | |
| 1.8.17 | 0 / 10 | |
| 1.8.16 | 0 / 10 | |
| 1.8.15 | 0 / 10 | |
| 1.8.14 | 0 / 10 | |
| 1.8.13 | 0 / 10 | |
| 1.8.12 | 0 / 10 | |
| 1.8.11 | 0 / 10 | |
| 1.8.10 | 0 / 10 | |
| 1.8.9 | 0 / 10 | |
| 1.8.8 | 0 / 10 | |
| 1.8.7 | 0 / 10 | |
| 1.8.6 | 0 / 10 | |
| 1.8.5 | 0 / 10 | |
| 1.8.4 | 0 / 10 | |
| 1.8.3 | 0 / 10 | |
| 1.8.2 | 0 / 10 | |
| 1.8.1 | 0 / 10 | |
| 1.8.0 | 0 / 10 | |
| 1.7.20 | 0 / 10 | |
| 1.7.19 | 0 / 10 | |
| 1.7.18 | 0 / 10 | |
| 1.7.17 | 0 / 10 |
v1.9.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.