@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 — the axios compromise (March 2026) relied on exactly this gap.
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 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 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 |
v1.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.97
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.96
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.95
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.94
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.93
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.92
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.91
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.90
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.89
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.87
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.86
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.85
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.83
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.