@univerjs/sheets-drawing
| Package Name | UMD Namespace | Version | License | Downloads | Contains CSS | Contains i18n locales | | --- | --- | --- | --- | --- | :---: | :---: | | `@univerjs/sheets-drawing` | `UniverSheetsDrawing` | [![][npm-version-shield]][npm-version-link] | ![
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | source-size-tripled | AI (source-diff): Size increase explained by addition of facade.js across 4 output formats (CJS/ESM/UMD/lib). | ai | |
| source-diff | obfuscated-file:lib/cjs/facade.js | AI (source-diff): Standard minified build artifact for @univerjs monorepo; no malicious patterns in code. | ai | |
| source-diff | obfuscated-file:lib/es/facade.js | AI (source-diff): Standard minified ESM build artifact; readable Babel-transpiled TypeScript with known @univerjs imports. | ai | |
| source-diff | obfuscated-file:lib/facade.js | AI (source-diff): Standard minified ESM build artifact; same pattern as other output formats. | ai | |
| source-diff | obfuscated-file:lib/umd/facade.js | AI (source-diff): Standard minified UMD build artifact; no suspicious code. | ai | |
| dependencies | unvetted-dep:@univerjs/sheets | AI (dependencies): Sibling monorepo dep at matching version; expected pattern for @univerjs/* packages. | ai | |
| dependencies | unvetted-dep:@univerjs/drawing | AI (dependencies): Sibling monorepo dep at matching version; expected pattern for @univerjs/* packages. | ai | |
| dependencies | unvetted-dep:@univerjs/engine-render | AI (dependencies): Sibling monorepo dep at matching version; expected pattern for @univerjs/* packages. | ai | |
| dependencies | unvetted-dep:@univerjs/core | AI (dependencies): Sibling monorepo dep at matching version; expected pattern for @univerjs/* packages. | ai |
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 0.22.1 | 4 / 3 | |
| 0.22.0 | 4 / 3 | |
| 0.21.1 | 4 / 3 | |
| 0.21.0 | 4 / 3 | |
| 0.20.1 | 4 / 3 | |
| 0.20.0 | 4 / 3 | |
| 0.19.0 | 3 / 3 | |
| 0.18.0 | 3 / 3 | |
| 0.17.0 | 3 / 4 | |
| 0.16.1 | 3 / 4 | |
| 0.16.0 | 3 / 4 | |
| 0.15.5 | 3 / 4 | |
| 0.15.4 | 3 / 4 | |
| 0.15.3 | 3 / 4 | |
| 0.15.2 | 3 / 4 | |
| 0.15.1 | 3 / 4 | |
| 0.15.0 | 3 / 4 | |
| 0.14.0 | 3 / 4 | |
| 0.13.0 | 3 / 4 | |
| 0.12.4 | 3 / 4 | |
| 0.12.3 | 3 / 4 | |
| 0.12.2 | 3 / 4 | |
| 0.12.1 | 3 / 4 | |
| 0.12.0 | 3 / 4 | |
| 0.11.0 | 3 / 4 | |
| 0.10.14 | 3 / 4 | |
| 0.10.13 | 3 / 4 | |
| 0.10.12 | 2 / 5 | |
| 0.10.11 | 2 / 5 | |
| 0.10.10 | 2 / 5 | |
| 0.10.9 | 2 / 5 | |
| 0.10.8 | 2 / 5 | |
| 0.10.7 | 2 / 5 | |
| 0.10.6 | 2 / 5 | |
| 0.10.5 | 2 / 5 | |
| 0.10.4 | 2 / 5 | |
| 0.10.3 | 2 / 5 | |
| 0.10.2 | 2 / 5 | |
| 0.10.1 | 2 / 5 | |
| 0.10.0 | 2 / 5 | |
| 0.9.4 | 2 / 5 | |
| 0.9.3 | 2 / 5 | |
| 0.9.2 | 2 / 5 | |
| 0.9.1 | 2 / 5 | |
| 0.9.0 | 2 / 5 | |
| 0.8.3 | 2 / 5 | |
| 0.8.2 | 2 / 5 | |
| 0.8.1 | 2 / 5 | |
| 0.8.0 | 2 / 5 | |
| 0.7.0 | 2 / 5 |
v0.22.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.22.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.21.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.21.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.1
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.