@univerjs/preset-sheets-core
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:lib/umd/locales/fr-FR.js | AI (source-diff): Minified UMD locale bundle with plain French strings; benign build output. | ai | |
| source-diff | obfuscated-file:lib/umd/locales/id-ID.js | AI (source-diff): UMD locale bundle with i18n strings; standard minified build output for @univerjs presets. | ai | |
| source-diff | obfuscated-file:lib/umd/locales/pt-BR.js | AI (source-diff): UMD locale bundle with i18n strings; standard minified build output for @univerjs presets. | ai | |
| source-diff | obfuscated-file:lib/umd/locales/ar-SA.js | AI (source-diff): UMD locale bundle with i18n strings; standard minified build output for @univerjs presets. | ai | |
| source-diff | obfuscated-file:lib/umd/locales/de-DE.js | AI (source-diff): UMD locale bundle with i18n strings; standard minified build output for @univerjs presets. | ai | |
| source-diff | obfuscated-file:lib/umd/locales/pl-PL.js | AI (source-diff): UMD locale bundle with i18n strings; standard minified build output for @univerjs presets. | ai | |
| source-diff | obfuscated-file:lib/umd/locales/it-IT.js | AI (source-diff): UMD locale bundle with i18n strings; standard minified build output for @univerjs presets. | ai | |
| source-diff | obfuscated-file:lib/umd/locales/zh-HK.js | AI (source-diff): UMD locale bundle with i18n strings; standard minified build output for @univerjs presets. | 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/locales/ko-KR.js | AI (source-diff): Minified UMD locale bundle with i18n strings only; standard build output for this package. | ai | |
| source-diff | obfuscated-file:lib/umd/locales/ca-ES.js | AI (source-diff): Minified UMD locale bundle with i18n strings only; standard build output for this package. | ai | |
| source-diff | obfuscated-file:lib/umd/locales/es-ES.js | AI (source-diff): Minified UMD locale bundle with i18n strings only; standard build output for this package. | ai | |
| source-diff | obfuscated-file:lib/umd/locales/ja-JP.js | AI (source-diff): Minified UMD locale bundle with i18n strings only; standard build output for this package. | ai | |
| source-diff | obfuscated-file:lib/umd/locales/sk-SK.js | AI (source-diff): Minified UMD locale bundle with i18n strings only; standard build output for this package. | ai | |
| dependencies | unvetted-dep:@univerjs/rpc | AI (dependencies): Same-monorepo sibling dep pinned to matching version; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@univerjs/sheets-formula | AI (dependencies): Same-monorepo sibling dep pinned to matching version; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@univerjs/engine-formula | AI (dependencies): Same-monorepo sibling dep pinned to matching version; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@univerjs/sheets-numfmt | AI (dependencies): Same-monorepo sibling dep pinned to matching version; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@univerjs/sheets-ui | AI (dependencies): Same-monorepo sibling dep pinned to matching version; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@univerjs/network | AI (dependencies): Same-monorepo sibling dep pinned to matching version; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@univerjs/design | AI (dependencies): Same-monorepo sibling dep pinned to matching version; not a third-party risk. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 0.25.1 | 14 / 6 | |
| 0.25.0 | 14 / 6 | |
| 0.24.0 | 14 / 6 | |
| 0.23.0 | 14 / 6 | |
| 0.22.1 | 14 / 6 | |
| 0.22.0 | 14 / 6 | |
| 0.21.1 | 14 / 6 | |
| 0.21.0 | 14 / 6 | |
| 0.20.1 | 14 / 6 | |
| 0.20.0 | 14 / 6 | |
| 0.19.0 | 14 / 6 | |
| 0.18.0 | 14 / 6 | |
| 0.17.0 | 14 / 6 | |
| 0.16.1 | 14 / 6 | |
| 0.16.0 | 14 / 6 | |
| 0.15.5 | 14 / 6 | |
| 0.15.4 | 14 / 6 | |
| 0.15.3 | 14 / 6 | |
| 0.15.2 | 14 / 6 | |
| 0.15.1 | 14 / 6 | |
| 0.15.0 | 14 / 6 | |
| 0.14.0 | 14 / 6 | |
| 0.13.0 | 14 / 6 | |
| 0.12.4 | 14 / 6 | |
| 0.12.3 | 14 / 6 | |
| 0.12.2 | 14 / 6 | |
| 0.12.1 | 14 / 6 | |
| 0.12.0 | 14 / 6 | |
| 0.11.0 | 14 / 6 | |
| 0.10.14 | 14 / 6 | |
| 0.8.2 | 15 / 6 | |
| 0.8.1 | 15 / 6 | |
| 0.8.0 | 15 / 6 | |
| 0.7.0 | 15 / 6 | |
| 0.6.10 | 14 / 5 | |
| 0.6.9 | 14 / 5 | |
| 0.6.8 | 14 / 5 | |
| 0.6.7 | 14 / 5 | |
| 0.6.6 | 14 / 5 | |
| 0.6.5 | 14 / 3 | |
| 0.6.4 | 13 / 3 | |
| 0.6.3 | 13 / 3 | |
| 0.6.2 | 13 / 3 | |
| 0.6.1 | 13 / 3 | |
| 0.6.0 | 13 / 3 | |
| 0.5.5 | 14 / 3 | |
| 0.5.4 | 14 / 3 | |
| 0.5.3 | 14 / 3 | |
| 0.5.2 | 14 / 3 | |
| 0.5.1 | 14 / 3 | |
| 0.5.0 | 14 / 3 |
v0.25.1
8 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.10
2 findingsNewly 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.6.9
2 findingsNewly 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.6.8
2 findingsNewly 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.6.7
2 findingsNewly 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.6.6
2 findingsNewly 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.6.5
2 findingsNewly 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.6.4
2 findingsNewly 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.6.3
2 findingsNewly 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.6.2
2 findingsNewly 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.6.1
2 findingsNewly 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.6.0
2 findingsNewly 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.5.5
2 findingsNewly 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.5.4
2 findingsNewly 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.5.3
2 findingsNewly 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.5.2
2 findingsNewly 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.5.1
2 findingsNewly 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.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.