@ecan-bi/pivot-table
### 项目开发指南 ``` // 下载项目依赖（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): Org-scoped internal BI component; lack of provenance is consistent across all versions and not a risk indicator here. | ai | |
| phantom-deps | phantom-dep:@ecan-bi/datav | AI (phantom-deps): Same-org dependency; phantom detection is a false positive for this package's build pattern. | ai | |
| phantom-deps | phantom-dep:@visactor/vtable | AI (phantom-deps): Referenced in config files only; consistent with bundled/peer usage pattern across versions. | ai | |
| phantom-deps | phantom-dep:@visactor/vtable-export | AI (phantom-deps): Referenced in config files only; consistent with bundled/peer usage pattern across versions. | ai | |
| phantom-deps | phantom-dep:monaco-editor | AI (phantom-deps): Listed in both dependencies and devDependencies; config-file reference is a stable false positive. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.1.8 | 5 / 31 | |
| 1.1.7 | 5 / 31 | |
| 1.1.6 | 5 / 31 | |
| 1.1.5 | 5 / 31 | |
| 1.1.4 | 5 / 31 | |
| 1.1.3 | 5 / 31 |
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.