@univerjs/sheets-table-ui
A library for connect and bind data from other sources to Univer Sheets
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/umd/locale/de-DE.js | AI (source-diff): UMD-wrapped locale strings; standard build output for @univerjs packages. | ai | |
| source-diff | large-new-source-files | AI (source-diff): New locale files added for additional language support; expected growth pattern. | ai | |
| source-diff | obfuscated-file:lib/umd/locale/pt-BR.js | AI (source-diff): UMD-wrapped locale strings; standard build output for @univerjs packages. | ai | |
| source-diff | obfuscated-file:lib/umd/locale/pl-PL.js | AI (source-diff): UMD-wrapped locale strings; standard build output for @univerjs packages. | ai | |
| source-diff | obfuscated-file:lib/umd/locale/it-IT.js | AI (source-diff): UMD-wrapped locale strings; standard build output for @univerjs packages. | ai | |
| source-diff | obfuscated-file:lib/umd/locale/id-ID.js | AI (source-diff): UMD-wrapped locale strings; standard build output for @univerjs packages. | ai | |
| phantom-deps | phantom-dep:@univerjs/icons | AI (phantom-deps): Same-org monorepo dependency; phantom-dep heuristic not applicable to internal module structures. | ai | |
| phantom-deps | phantom-dep:@univerjs/design | AI (phantom-deps): Same-org monorepo dependency; phantom-dep heuristic not applicable to internal module structures. | ai | |
| phantom-deps | phantom-dep:@univerjs/sheets-sort | AI (phantom-deps): Same-org monorepo dependency; phantom-dep heuristic not applicable to internal module structures. | ai | |
| phantom-deps | phantom-dep:@univerjs/engine-formula | AI (phantom-deps): Same-org monorepo dependency; phantom-dep heuristic not applicable to internal module structures. | ai | |
| phantom-deps | phantom-dep:@univerjs/sheets-formula-ui | AI (phantom-deps): Same-org monorepo dependency; phantom-dep heuristic not applicable to internal module structures. | ai | |
| dependencies | unvetted-dep:@univerjs/ui | AI (dependencies): Sibling package in the @univerjs monorepo; unvetted status reflects pipeline lag, not risk. | ai | |
| dependencies | unvetted-dep:@univerjs/sheets | AI (dependencies): Sibling package in the @univerjs monorepo; unvetted status reflects pipeline lag, not risk. | ai | |
| dependencies | unvetted-dep:@univerjs/design | AI (dependencies): Sibling package in the @univerjs monorepo; unvetted status reflects pipeline lag, not risk. | ai | |
| dependencies | unvetted-dep:@univerjs/icons | AI (dependencies): Sibling package in the @univerjs monorepo; unvetted status reflects pipeline lag, not risk. | ai | |
| dependencies | unvetted-dep:@univerjs/core | AI (dependencies): Sibling package in the @univerjs monorepo; unvetted status reflects pipeline lag, not risk. | ai | |
| dependencies | unvetted-dep:@univerjs/sheets-sort | AI (dependencies): Sibling package in the @univerjs monorepo; unvetted status reflects pipeline lag, not risk. | ai | |
| dependencies | unvetted-dep:@univerjs/sheets-ui | AI (dependencies): Sibling package in the @univerjs monorepo; unvetted status reflects pipeline lag, not risk. | ai | |
| dependencies | unvetted-dep:@univerjs/sheets-table | AI (dependencies): Sibling package in the @univerjs monorepo; unvetted status reflects pipeline lag, not risk. | ai | |
| dependencies | unvetted-dep:@univerjs/engine-render | AI (dependencies): Sibling package in the @univerjs monorepo; unvetted status reflects pipeline lag, not risk. | ai | |
| dependencies | unvetted-dep:@univerjs/engine-formula | AI (dependencies): Sibling package in the @univerjs monorepo; unvetted status reflects pipeline lag, not risk. | ai | |
| dependencies | unvetted-dep:@univerjs/sheets-formula-ui | AI (dependencies): Sibling package in the @univerjs monorepo; unvetted status reflects pipeline lag, not risk. | ai |
Versions (showing 51 of 53)
| Version | Deps | Published |
|---|---|---|
| 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 | |
| 0.10.13 | 11 / 8 | |
| 0.10.12 | 11 / 8 | |
| 0.10.11 | 11 / 8 | |
| 0.10.10 | 11 / 8 | |
| 0.10.9 | 11 / 8 | |
| 0.10.8 | 11 / 8 | |
| 0.10.7 | 11 / 8 | |
| 0.10.6 | 11 / 8 | |
| 0.10.5 | 11 / 8 | |
| 0.10.4 | 11 / 8 | |
| 0.10.3 | 11 / 8 | |
| 0.10.2 | 11 / 8 | |
| 0.10.1 | 11 / 8 | |
| 0.10.0 | 11 / 8 | |
| 0.9.4 | 11 / 8 | |
| 0.9.3 | 11 / 8 | |
| 0.9.2 | 11 / 8 | |
| 0.9.1 | 11 / 8 | |
| 0.9.0 | 11 / 8 | |
| 0.8.3 | 11 / 8 | |
| 0.8.2 | 11 / 8 | |
| 0.8.1 | 11 / 8 |
v0.25.0
6 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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.23.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.0
1 findingPackage 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.
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.