@univerjs/sheets-formula-ui
| Package Name | UMD Namespace | Version | License | Downloads | Contains CSS | Contains i18n locales | | --- | --- | --- | --- | --- | :---: | :---: | | `@univerjs/sheets-formula-ui` | `UniverSheetsFormulaUi` | [![][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 | obfuscated-file:lib/es/locale/ja-JP.js | AI (source-diff): Minified locale string dictionary, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/locale/sk-SK.js | AI (source-diff): Minified locale string dictionary, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/es/locale/sk-SK.js | AI (source-diff): Minified locale string dictionary, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/locale/ja-JP.js | AI (source-diff): Minified locale string dictionary, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/umd/locale/sk-SK.js | AI (source-diff): Minified UMD Slovak locale bundle, benign. | ai | |
| source-diff | obfuscated-file:lib/cjs/locale/sk-SK.js | AI (source-diff): Minified Slovak locale dictionary, benign. | ai | |
| source-diff | obfuscated-file:lib/cjs/locale/ja-JP.js | AI (source-diff): Minified locale data (Japanese formula strings), not obfuscation; stable build output. | ai | |
| source-diff | obfuscated-file:lib/umd/locale/ja-JP.js | AI (source-diff): Minified UMD locale bundle; legit i18n data, no payload. | ai | |
| phantom-deps | phantom-dep:@univerjs/docs | AI (phantom-deps): Monorepo peer dependency; stable pattern for @univerjs packages. | ai | |
| phantom-deps | phantom-dep:@univerjs/icons | AI (phantom-deps): Monorepo peer dependency; stable pattern for @univerjs packages. | ai | |
| phantom-deps | phantom-dep:@univerjs/design | AI (phantom-deps): Monorepo peer dependency; stable pattern for @univerjs packages. | ai | |
| dependencies | unvetted-dep:@univerjs/ui | AI (dependencies): Internal monorepo sibling package; risk tracks with the parent project. | ai | |
| dependencies | unvetted-dep:@univerjs/docs | AI (dependencies): Internal monorepo sibling package; risk tracks with the parent project. | ai | |
| dependencies | unvetted-dep:@univerjs/core | AI (dependencies): Internal monorepo sibling package; risk tracks with the parent project. | ai | |
| dependencies | unvetted-dep:@univerjs/engine-render | AI (dependencies): Internal monorepo sibling package; risk tracks with the parent project. | ai | |
| dependencies | unvetted-dep:@univerjs/sheets-ui | AI (dependencies): Internal monorepo sibling package; risk tracks with the parent project. | ai | |
| dependencies | unvetted-dep:@univerjs/docs-ui | AI (dependencies): Internal monorepo sibling package; risk tracks with the parent project. | ai | |
| dependencies | unvetted-dep:@univerjs/sheets | AI (dependencies): Internal monorepo sibling package; risk tracks with the parent project. | ai | |
| dependencies | unvetted-dep:@univerjs/design | AI (dependencies): Internal monorepo sibling package; risk tracks with the parent project. | ai | |
| dependencies | unvetted-dep:@univerjs/icons | AI (dependencies): Internal monorepo sibling package; risk tracks with the parent project. | ai | |
| dependencies | unvetted-dep:@univerjs/engine-formula | AI (dependencies): Internal monorepo sibling package; risk tracks with the parent project. | ai | |
| dependencies | unvetted-dep:@univerjs/sheets-formula | AI (dependencies): Internal monorepo sibling package; risk tracks with the parent project. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 0.25.1 | 11 / 7 | |
| 0.25.0 | 11 / 7 | |
| 0.24.0 | 11 / 7 | |
| 0.23.0 | 11 / 7 | |
| 0.22.1 | 11 / 7 | |
| 0.22.0 | 11 / 7 | |
| 0.21.1 | 11 / 7 | |
| 0.21.0 | 11 / 7 | |
| 0.20.1 | 11 / 7 | |
| 0.20.0 | 11 / 7 | |
| 0.19.0 | 11 / 7 | |
| 0.18.0 | 11 / 7 | |
| 0.17.0 | 11 / 8 | |
| 0.16.1 | 11 / 8 | |
| 0.16.0 | 11 / 8 | |
| 0.15.5 | 11 / 8 | |
| 0.15.4 | 11 / 8 | |
| 0.15.3 | 11 / 8 | |
| 0.15.2 | 11 / 8 | |
| 0.15.1 | 11 / 8 | |
| 0.15.0 | 11 / 8 | |
| 0.14.0 | 11 / 8 | |
| 0.13.0 | 11 / 8 | |
| 0.12.4 | 11 / 8 | |
| 0.12.3 | 11 / 8 | |
| 0.12.2 | 11 / 8 | |
| 0.12.1 | 11 / 8 | |
| 0.12.0 | 11 / 8 | |
| 0.11.0 | 11 / 8 | |
| 0.10.14 | 11 / 8 |
v0.25.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.18.0
9 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.
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.
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.17.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.16.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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.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.15.5
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.15.4
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.15.3
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.4
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.