@univerjs-pro/sheets-chart
Chart library for Univer.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Bundler-generated CJS loader pattern, stable across Univer packages. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Part of javascript-obfuscator output across the @univerjs-pro package family; not an independent malicious payload. | ai | |
| phantom-deps | phantom-dep:@univerjs/sheets-drawing | AI (phantom-deps): Config-file reference in monorepo; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@univerjs/engine-formula | AI (phantom-deps): Config-file reference in monorepo; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@univerjs-pro/license | AI (phantom-deps): Same-org scoped dependency; typical in monorepo patterns where shared licenses are declared but not directly imported. | ai | |
| semgrep | semgrep:obfuscation-while-true | AI (semgrep): DreamNum intentionally obfuscates facade.js for license enforcement; stable pattern across all @univerjs-pro packages. | ai | |
| semgrep | semgrep:obfuscation-hex-functions | AI (semgrep): Same deliberate obfuscation of facade.js for commercial license protection; stable for this package family. | ai |
Versions (showing 71 of 71)
| Version | Deps | Published |
|---|---|---|
| 0.25.1 | 6 / 5 | |
| 0.25.0 | 6 / 5 | |
| 0.24.0 | 6 / 5 | |
| 0.23.0 | 6 / 5 | |
| 0.22.1 | 6 / 5 | |
| 0.22.0 | 6 / 5 | |
| 0.21.1 | 6 / 5 | |
| 0.21.0 | 6 / 5 | |
| 0.20.1 | 6 / 5 | |
| 0.20.0 | 6 / 5 | |
| 0.19.0 | 4 / 4 | |
| 0.18.0 | 4 / 4 | |
| 0.17.0 | 4 / 5 | |
| 0.16.1 | 4 / 5 | |
| 0.16.0 | 4 / 5 | |
| 0.15.5 | 4 / 5 | |
| 0.15.4 | 4 / 5 | |
| 0.15.3 | 4 / 5 | |
| 0.15.2 | 4 / 5 | |
| 0.15.1 | 4 / 5 | |
| 0.15.0 | 4 / 6 | |
| 0.14.0 | 4 / 6 | |
| 0.13.0 | 4 / 6 | |
| 0.12.4 | 4 / 6 | |
| 0.12.3 | 4 / 6 | |
| 0.12.2 | 4 / 6 | |
| 0.12.1 | 4 / 6 | |
| 0.12.0 | 4 / 6 | |
| 0.11.0 | 4 / 6 | |
| 0.10.14 | 4 / 6 | |
| 0.10.13 | 4 / 6 | |
| 0.10.12 | 4 / 6 | |
| 0.10.11 | 4 / 6 | |
| 0.10.10 | 4 / 6 | |
| 0.10.9 | 4 / 6 | |
| 0.10.8 | 4 / 6 | |
| 0.10.7 | 4 / 6 | |
| 0.10.6 | 4 / 6 | |
| 0.10.5 | 4 / 6 | |
| 0.10.4 | 4 / 6 | |
| 0.10.3 | 4 / 6 | |
| 0.10.2 | 4 / 6 | |
| 0.10.1 | 4 / 6 | |
| 0.10.0 | 4 / 6 | |
| 0.9.4 | 4 / 6 | |
| 0.9.3 | 4 / 6 | |
| 0.9.2 | 4 / 6 | |
| 0.9.1 | 4 / 6 | |
| 0.9.0 | 4 / 6 | |
| 0.8.3 | 4 / 6 | |
| 0.8.2 | 4 / 6 | |
| 0.8.1 | 4 / 6 | |
| 0.8.0 | 4 / 6 | |
| 0.7.0 | 4 / 6 | |
| 0.6.10 | 4 / 6 | |
| 0.6.9 | 4 / 6 | |
| 0.6.8 | 4 / 6 | |
| 0.6.7 | 4 / 6 | |
| 0.6.6 | 4 / 6 | |
| 0.6.5 | 4 / 6 | |
| 0.6.4 | 3 / 6 | |
| 0.6.3 | 3 / 6 | |
| 0.6.2 | 3 / 6 | |
| 0.6.1 | 3 / 6 | |
| 0.6.0 | 3 / 6 | |
| 0.5.5 | 3 / 6 | |
| 0.5.4 | 3 / 6 | |
| 0.5.3 | 3 / 6 | |
| 0.5.2 | 3 / 6 | |
| 0.5.1 | 2 / 6 | |
| 0.5.0 | 2 / 6 |
v0.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.