@univerjs/data-validation
Data validation library for Univer
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 | source-size-tripled | AI (source-diff): Size increase from adding UMD locale bundles; expected for this package. | ai | |
| source-diff | obfuscated-file:lib/umd/locale/ar-SA.js | AI (source-diff): UMD-wrapped i18n locale strings, not obfuscated code; stable pattern for this package. | ai | |
| source-diff | obfuscated-file:lib/umd/locale/ca-ES.js | AI (source-diff): UMD-wrapped i18n locale strings, not obfuscated code. | ai | |
| source-diff | obfuscated-file:lib/umd/locale/de-DE.js | AI (source-diff): UMD-wrapped i18n locale strings, not obfuscated code. | ai | |
| source-diff | obfuscated-file:lib/umd/locale/en-US.js | AI (source-diff): UMD-wrapped i18n locale strings, not obfuscated code. | ai | |
| source-diff | obfuscated-file:lib/umd/locale/es-ES.js | AI (source-diff): UMD-wrapped i18n locale strings, not obfuscated code. | ai | |
| source-diff | obfuscated-file:lib/umd/locale/fa-IR.js | AI (source-diff): UMD-wrapped i18n locale strings, not obfuscated code. | ai | |
| source-diff | obfuscated-file:lib/umd/locale/fr-FR.js | AI (source-diff): UMD-wrapped i18n locale strings, not obfuscated code. | ai | |
| source-diff | obfuscated-file:lib/umd/locale/id-ID.js | AI (source-diff): UMD-wrapped i18n locale strings, not obfuscated code. | ai | |
| source-diff | obfuscated-file:lib/umd/locale/it-IT.js | AI (source-diff): UMD-wrapped i18n locale strings, not obfuscated code. | ai | |
| source-diff | obfuscated-file:lib/umd/locale/ja-JP.js | AI (source-diff): UMD-wrapped i18n locale strings, not obfuscated code. | ai | |
| source-diff | obfuscated-file:lib/umd/locale/ko-KR.js | AI (source-diff): UMD-wrapped i18n locale strings, not obfuscated code. | ai | |
| source-diff | obfuscated-file:lib/umd/locale/pl-PL.js | AI (source-diff): UMD-wrapped i18n locale strings, not obfuscated code. | ai | |
| source-diff | large-new-source-files | AI (source-diff): New locale UMD bundles added for i18n support; expected growth. | ai | |
| dependencies | unvetted-dep:@univerjs/core | AI (dependencies): Sibling package from the same Univer monorepo; unvetted status is a pipeline gap, not a real risk. | ai |
Versions (showing 51 of 53)
| Version | Deps | Published |
|---|---|---|
| 0.25.0 | 1 / 6 | |
| 0.24.0 | 1 / 6 | |
| 0.23.0 | 1 / 6 | |
| 0.22.1 | 1 / 6 | |
| 0.22.0 | 1 / 6 | |
| 0.21.1 | 1 / 6 | |
| 0.21.0 | 1 / 6 | |
| 0.20.1 | 1 / 6 | |
| 0.20.0 | 1 / 6 | |
| 0.19.0 | 1 / 6 | |
| 0.18.0 | 1 / 6 | |
| 0.17.0 | 1 / 8 | |
| 0.16.1 | 1 / 8 | |
| 0.16.0 | 1 / 8 | |
| 0.15.5 | 1 / 8 | |
| 0.15.4 | 1 / 8 | |
| 0.15.3 | 1 / 8 | |
| 0.15.2 | 1 / 8 | |
| 0.15.1 | 1 / 8 | |
| 0.15.0 | 1 / 8 | |
| 0.14.0 | 1 / 8 | |
| 0.13.0 | 1 / 8 | |
| 0.12.4 | 1 / 8 | |
| 0.12.3 | 1 / 8 | |
| 0.12.2 | 1 / 8 | |
| 0.12.1 | 1 / 8 | |
| 0.12.0 | 1 / 8 | |
| 0.11.0 | 1 / 8 | |
| 0.10.14 | 1 / 8 | |
| 0.10.13 | 1 / 8 | |
| 0.10.12 | 1 / 8 | |
| 0.10.11 | 1 / 8 | |
| 0.10.10 | 1 / 8 | |
| 0.10.9 | 1 / 8 | |
| 0.10.8 | 1 / 8 | |
| 0.10.7 | 1 / 8 | |
| 0.10.6 | 1 / 8 | |
| 0.10.5 | 1 / 8 | |
| 0.10.4 | 1 / 8 | |
| 0.10.3 | 1 / 8 | |
| 0.10.2 | 1 / 8 | |
| 0.10.1 | 1 / 8 | |
| 0.10.0 | 1 / 8 | |
| 0.9.4 | 1 / 8 | |
| 0.9.3 | 1 / 8 | |
| 0.9.2 | 1 / 8 | |
| 0.9.1 | 1 / 8 | |
| 0.9.0 | 1 / 8 | |
| 0.8.3 | 1 / 8 | |
| 0.8.2 | 1 / 8 | |
| 0.8.1 | 1 / 8 |
v0.25.0
13 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.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. 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. 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.