@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 — the axios compromise (March 2026) relied on exactly this gap.
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/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/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/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/engine-formula | AI (dependencies): Same-monorepo sibling dep pinned to matching version; not a third-party risk. | 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/design | 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/sheets-ui | 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 |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 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.8.2 | 15 / 6 | |
| 0.8.1 | 15 / 6 | |
| 0.8.0 | 15 / 6 | |
| 0.7.0 | 15 / 6 |
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.1
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.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.
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.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.