@ecan-bi/datav
### 项目开发指南 ``` // 下载项目依赖（node_modules） yarn install --registry=https://registry.npm.taobao.org
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established org-scoped package with long history; lack of Sigstore provenance is not a disqualifier here. | ai | |
| phantom-deps | phantom-dep:vant | AI (phantom-deps): Referenced in config files; stable false positive for this UI component library. | ai | |
| phantom-deps | phantom-dep:marked | AI (phantom-deps): Config-file reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@ecan-bi/indicator-library | AI (phantom-deps): Same org scope; loaded by convention, not a threat. | ai | |
| phantom-deps | phantom-dep:vue3-virtual-scroller | AI (phantom-deps): Config-file reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/big.js | AI (phantom-deps): Framework-scoped types package; loaded by convention, not a threat. | ai | |
| phantom-deps | phantom-dep:lottie-web | AI (phantom-deps): Config-file reference; stable false positive for this package. | ai |
Versions (showing 100 of 380)
| Version | Deps | Published |
|---|---|---|
| 1.6.27 | 16 / 46 | |
| 1.6.26 | 16 / 46 | |
| 1.6.25 | 16 / 46 | |
| 1.6.24 | 16 / 46 | |
| 1.6.23 | 16 / 46 | |
| 1.6.22 | 16 / 46 | |
| 1.6.21 | 16 / 46 | |
| 1.6.20 | 16 / 46 | |
| 1.6.19 | 16 / 46 | |
| 1.6.18 | 16 / 46 | |
| 1.6.17 | 16 / 46 | |
| 1.6.16 | 16 / 46 | |
| 1.6.15 | 16 / 46 | |
| 1.6.14 | 15 / 47 | |
| 1.6.12 | 15 / 47 | |
| 1.6.11 | 15 / 47 | |
| 1.6.10 | 15 / 47 | |
| 1.6.9 | 15 / 47 | |
| 1.6.8 | 15 / 47 | |
| 1.6.6 | 15 / 47 | |
| 1.6.5 | 15 / 47 | |
| 1.6.4 | 15 / 47 | |
| 1.6.3 | 15 / 47 | |
| 1.6.2 | 15 / 47 | |
| 1.6.1 | 15 / 47 | |
| 1.5.97 | 15 / 47 | |
| 1.5.96 | 15 / 47 | |
| 1.5.95 | 14 / 47 | |
| 1.5.94 | 14 / 47 | |
| 1.5.93 | 14 / 47 | |
| 1.5.92 | 14 / 47 | |
| 1.5.91 | 14 / 47 | |
| 1.5.90 | 14 / 47 | |
| 1.5.89 | 14 / 47 | |
| 1.5.88 | 14 / 47 | |
| 1.5.87 | 14 / 47 | |
| 1.5.86 | 14 / 47 | |
| 1.5.85 | 14 / 47 | |
| 1.5.84 | 14 / 47 | |
| 1.5.83 | 14 / 47 | |
| 1.5.82 | 14 / 47 | |
| 1.5.81 | 13 / 47 | |
| 1.5.80 | 13 / 47 | |
| 1.5.79 | 13 / 47 | |
| 1.5.78 | 13 / 47 | |
| 1.5.77 | 13 / 47 | |
| 1.5.76 | 13 / 47 | |
| 1.5.75 | 13 / 47 | |
| 1.5.74 | 13 / 47 | |
| 1.5.73 | 13 / 47 | |
| 1.5.72 | 13 / 47 | |
| 1.5.71 | 13 / 47 | |
| 1.5.70 | 13 / 47 | |
| 1.5.69 | 13 / 47 | |
| 1.5.68 | 13 / 47 | |
| 1.5.67 | 13 / 47 | |
| 1.5.66 | 13 / 47 | |
| 1.5.65 | 13 / 47 | |
| 1.5.64 | 13 / 47 | |
| 1.5.63 | 13 / 47 | |
| 1.5.62 | 13 / 47 | |
| 1.5.61 | 13 / 47 | |
| 1.5.60 | 13 / 47 | |
| 1.5.59 | 13 / 47 | |
| 1.5.58 | 13 / 47 | |
| 1.5.57 | 13 / 47 | |
| 1.5.56 | 13 / 47 | |
| 1.5.55 | 13 / 47 | |
| 1.5.54 | 13 / 47 | |
| 1.5.53 | 13 / 47 | |
| 1.5.52 | 13 / 47 | |
| 1.5.51 | 13 / 47 | |
| 1.5.50 | 13 / 47 | |
| 1.5.49 | 13 / 47 | |
| 1.5.48 | 13 / 47 | |
| 1.5.47 | 13 / 47 | |
| 1.5.46 | 13 / 47 | |
| 1.5.45 | 13 / 47 | |
| 1.5.44 | 13 / 47 | |
| 1.5.43 | 13 / 47 | |
| 1.5.42 | 13 / 47 | |
| 1.5.41 | 13 / 47 | |
| 1.5.40 | 13 / 47 | |
| 1.5.39 | 13 / 47 | |
| 1.5.38 | 13 / 47 | |
| 1.5.37 | 13 / 47 | |
| 1.5.36 | 13 / 47 | |
| 1.5.35 | 13 / 47 | |
| 1.5.34 | 13 / 47 | |
| 1.5.33 | 13 / 47 | |
| 1.5.32 | 12 / 47 | |
| 1.5.31 | 12 / 47 | |
| 1.5.30 | 12 / 47 | |
| 1.5.29 | 12 / 47 | |
| 1.5.28 | 12 / 47 | |
| 1.5.27 | 12 / 47 | |
| 1.5.26 | 12 / 47 | |
| 1.5.25 | 12 / 47 | |
| 1.5.24 | 12 / 47 | |
| 1.5.23 | 12 / 47 |
v1.6.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.