@univerjs/preset-sheets-collaboration
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/es-ES.js | AI (source-diff): UMD locale string bundle; obfuscator output with only i18n text, no payload. | ai | |
| source-diff | obfuscated-file:lib/umd/locales/ca-ES.js | AI (source-diff): UMD locale string bundle; obfuscator output with only i18n text, no payload. | ai | |
| source-diff | obfuscated-file:lib/umd/locales/sk-SK.js | AI (source-diff): javascript-obfuscator output of vendored collaboration-client locale bundle; benign for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): UMD loader pattern for bundled sub-packages, dual-use and expected in this build format. | ai | |
| source-diff | obfuscated-file:lib/umd/locales/de-DE.js | AI (source-diff): UMD locale bundle obfuscated by javascript-obfuscator; contains only i18n strings. | ai | |
| source-diff | obfuscated-file:lib/umd/locales/ar-SA.js | AI (source-diff): UMD locale bundle obfuscated by javascript-obfuscator; contains only i18n strings. Stable pattern for this package. | ai | |
| source-diff | obfuscated-file:lib/umd/locales/id-ID.js | AI (source-diff): UMD locale bundle obfuscated by javascript-obfuscator; contains only i18n strings. | ai | |
| source-diff | obfuscated-file:lib/umd/locales/it-IT.js | AI (source-diff): UMD locale bundle obfuscated by javascript-obfuscator; contains only i18n strings. | ai | |
| source-diff | obfuscated-file:lib/umd/locales/pl-PL.js | AI (source-diff): UMD locale bundle obfuscated by javascript-obfuscator; contains only i18n strings. | ai | |
| source-diff | obfuscated-file:lib/umd/locales/pt-BR.js | AI (source-diff): UMD locale bundle obfuscated by javascript-obfuscator; contains only i18n strings. | ai | |
| source-diff | obfuscated-file:lib/umd/locales/zh-HK.js | AI (source-diff): UMD locale bundle obfuscated by javascript-obfuscator; contains only i18n strings. | ai | |
| source-diff | large-new-source-files | AI (source-diff): New locale files added for additional languages; expected growth pattern for this preset package. | ai | |
| dependencies | unvetted-dep:@univerjs-pro/thread-comment-datasource | AI (dependencies): Same org (@univerjs-pro); stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@univerjs-pro/edit-history-loader | AI (dependencies): Same org (@univerjs-pro) as the publishing package; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@univerjs-pro/edit-history-viewer | AI (dependencies): Same org (@univerjs-pro); stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@univerjs-pro/collaboration-client | AI (dependencies): Same org (@univerjs-pro); stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@univerjs-pro/collaboration-client-ui | AI (dependencies): Same org (@univerjs-pro); stable pattern across versions. | ai | |
| phantom-deps | phantom-dep:@univerjs/preset-sheets-advanced | AI (phantom-deps): Same-org preset package; declared as dependency and used in config, not a phantom risk. | ai | |
| phantom-deps | phantom-dep:@univerjs-pro/thread-comment-datasource | AI (phantom-deps): Referenced in config files per finding; stable false positive for this package. | ai | |
| semgrep | semgrep:obfuscation-hex-functions | AI (semgrep): Commercial @univerjs-pro/* bundles intentionally obfuscated for IP protection; consistent across all versions. | ai | |
| semgrep | semgrep:obfuscation-while-true | AI (semgrep): Same obfuscated UMD bundle from @univerjs-pro/collaboration-client; stable pattern for this package. | ai |
Versions (showing 71 of 71)
| Version | Deps | Published |
|---|---|---|
| 0.25.1 | 7 / 6 | |
| 0.25.0 | 7 / 6 | |
| 0.24.0 | 7 / 6 | |
| 0.23.0 | 7 / 6 | |
| 0.22.1 | 7 / 6 | |
| 0.22.0 | 7 / 6 | |
| 0.21.1 | 7 / 6 | |
| 0.21.0 | 7 / 6 | |
| 0.20.1 | 7 / 6 | |
| 0.20.0 | 7 / 6 | |
| 0.19.0 | 7 / 6 | |
| 0.18.0 | 7 / 6 | |
| 0.17.0 | 7 / 6 | |
| 0.16.1 | 7 / 6 | |
| 0.16.0 | 7 / 6 | |
| 0.15.5 | 7 / 6 | |
| 0.15.4 | 7 / 6 | |
| 0.15.3 | 7 / 6 | |
| 0.15.2 | 7 / 6 | |
| 0.15.1 | 7 / 6 | |
| 0.15.0 | 7 / 6 | |
| 0.14.0 | 7 / 6 | |
| 0.13.0 | 7 / 6 | |
| 0.12.4 | 7 / 6 | |
| 0.12.3 | 7 / 6 | |
| 0.12.2 | 7 / 6 | |
| 0.12.1 | 7 / 6 | |
| 0.12.0 | 7 / 6 | |
| 0.11.0 | 7 / 6 | |
| 0.10.14 | 7 / 6 | |
| 0.10.13 | 7 / 6 | |
| 0.10.12 | 7 / 6 | |
| 0.10.11 | 7 / 6 | |
| 0.10.10 | 7 / 6 | |
| 0.10.9 | 7 / 6 | |
| 0.10.8 | 7 / 6 | |
| 0.10.7 | 7 / 6 | |
| 0.10.6 | 7 / 6 | |
| 0.10.5 | 7 / 6 | |
| 0.10.4 | 7 / 6 | |
| 0.10.3 | 7 / 6 | |
| 0.10.2 | 7 / 6 | |
| 0.10.1 | 7 / 6 | |
| 0.10.0 | 7 / 6 | |
| 0.9.4 | 7 / 6 | |
| 0.9.3 | 7 / 6 | |
| 0.9.2 | 7 / 6 | |
| 0.9.1 | 7 / 6 | |
| 0.9.0 | 7 / 6 | |
| 0.8.3 | 7 / 6 | |
| 0.8.2 | 7 / 6 | |
| 0.8.1 | 7 / 6 | |
| 0.8.0 | 7 / 6 | |
| 0.7.0 | 7 / 6 | |
| 0.6.10 | 7 / 5 | |
| 0.6.9 | 7 / 5 | |
| 0.6.8 | 7 / 5 | |
| 0.6.7 | 7 / 5 | |
| 0.6.6 | 7 / 5 | |
| 0.6.5 | 7 / 3 | |
| 0.6.4 | 7 / 3 | |
| 0.6.3 | 7 / 3 | |
| 0.6.2 | 7 / 3 | |
| 0.6.1 | 7 / 3 | |
| 0.6.0 | 7 / 3 | |
| 0.5.5 | 7 / 3 | |
| 0.5.4 | 7 / 3 | |
| 0.5.3 | 7 / 3 | |
| 0.5.2 | 7 / 3 | |
| 0.5.1 | 5 / 3 | |
| 0.5.0 | 5 / 3 |
v0.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator. Artifact: obfuscated (_0x-array) — true obfuscation signature.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator. Artifact: obfuscated (_0x-array) — true obfuscation signature.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.5
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator. Artifact: obfuscated (_0x-array) — true obfuscation signature.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator. Artifact: obfuscated (_0x-array) — true obfuscation signature.
Package 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.3
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.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.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.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator. Artifact: obfuscated (_0x-array) — true obfuscation signature.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator. Artifact: obfuscated (_0x-array) — true obfuscation signature.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator. Artifact: obfuscated (_0x-array) — true obfuscation signature.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator. Artifact: obfuscated (_0x-array) — true obfuscation signature.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator. Artifact: obfuscated (_0x-array) — true obfuscation signature.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator. Artifact: obfuscated (_0x-array) — true obfuscation signature.
Package 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.3
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.
v0.6.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.