@univerjs-pro/license
Univer License Management Library
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 |
|---|---|---|---|---|
| semgrep | semgrep:obfuscation-while-true | AI (semgrep): License management library intentionally obfuscates validation logic; stable pattern across all versions. | ai | |
| semgrep | semgrep:obfuscation-hex-functions | AI (semgrep): License management library intentionally obfuscates validation logic; stable pattern across all versions. | ai |
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 0.22.1 | 4 / 4 | |
| 0.22.0 | 4 / 4 | |
| 0.21.1 | 4 / 4 | |
| 0.21.0 | 4 / 4 | |
| 0.20.1 | 4 / 4 | |
| 0.20.0 | 4 / 4 | |
| 0.19.0 | 4 / 4 | |
| 0.18.0 | 4 / 4 | |
| 0.17.0 | 4 / 5 | |
| 0.16.1 | 4 / 5 | |
| 0.16.0 | 4 / 5 | |
| 0.15.5 | 4 / 5 | |
| 0.15.4 | 4 / 5 | |
| 0.15.3 | 4 / 5 | |
| 0.15.2 | 4 / 5 | |
| 0.15.1 | 4 / 5 | |
| 0.15.0 | 4 / 5 | |
| 0.14.0 | 4 / 5 | |
| 0.13.0 | 4 / 5 | |
| 0.12.4 | 4 / 5 | |
| 0.12.3 | 4 / 5 | |
| 0.12.2 | 4 / 5 | |
| 0.12.1 | 4 / 5 | |
| 0.12.0 | 4 / 5 | |
| 0.11.0 | 4 / 5 | |
| 0.10.14 | 4 / 5 | |
| 0.10.13 | 4 / 5 | |
| 0.10.12 | 4 / 5 | |
| 0.10.11 | 4 / 5 | |
| 0.10.10 | 4 / 5 | |
| 0.10.9 | 4 / 5 | |
| 0.10.8 | 4 / 5 | |
| 0.10.7 | 4 / 5 | |
| 0.10.6 | 4 / 5 | |
| 0.10.5 | 4 / 5 | |
| 0.10.4 | 4 / 5 | |
| 0.10.3 | 4 / 5 | |
| 0.10.2 | 4 / 5 | |
| 0.10.1 | 4 / 5 | |
| 0.10.0 | 4 / 5 | |
| 0.9.4 | 4 / 5 | |
| 0.9.3 | 4 / 5 | |
| 0.9.2 | 4 / 5 | |
| 0.9.1 | 4 / 5 | |
| 0.9.0 | 4 / 5 | |
| 0.8.3 | 4 / 5 | |
| 0.8.2 | 4 / 5 | |
| 0.8.1 | 4 / 5 | |
| 0.8.0 | 4 / 5 | |
| 0.7.0 | 4 / 5 |
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
10 findingswhile(!![]) loop is a signature of javascript-obfuscator output > 1 | const _0x3f6374=_0x789e;(function(_0x1c3ba0,_0x4831ef){const _0x363c25=_0x789e,_0x13e9fe=_0x1c3ba0();while(!![]){try{con
Hex-prefixed function names (_0x...) are generated by javascript-obfuscator > 1 | const _0x3f6374=_0x789e;(function(_0x1c3ba0,_0x4831ef){const _0x363c25=_0x789e,_0x13e9fe=_0x1c3ba0();while(!![]){try{con
Hex-prefixed function names (_0x...) are generated by javascript-obfuscator > 1 | const _0x3f6374=_0x789e;(function(_0x1c3ba0,_0x4831ef){const _0x363c25=_0x789e,_0x13e9fe=_0x1c3ba0();while(!![]){try{con
Hex-prefixed function names (_0x...) are generated by javascript-obfuscator > 1 | const _0x26d700=_0x176d;function _0x1e3d(){const _0x4edcee=['from','join','5159HJXDuY','_valid','_env','rotate','fillRec
while(!![]) loop is a signature of javascript-obfuscator output > 1 | const _0x26d700=_0x176d;function _0x1e3d(){const _0x4edcee=['from','join','5159HJXDuY','_valid','_env','rotate','fillRec
Hex-prefixed function names (_0x...) are generated by javascript-obfuscator > 1 | const _0x26d700=_0x176d;function _0x1e3d(){const _0x4edcee=['from','join','5159HJXDuY','_valid','_env','rotate','fillRec
Hex-prefixed function names (_0x...) are generated by javascript-obfuscator > 1 | const _0x26d700=_0x176d;function _0x1e3d(){const _0x4edcee=['from','join','5159HJXDuY','_valid','_env','rotate','fillRec
while(!![]) loop is a signature of javascript-obfuscator output > 1 | const _0x26d700=_0x176d;function _0x1e3d(){const _0x4edcee=['from','join','5159HJXDuY','_valid','_env','rotate','fillRec
Hex-prefixed function names (_0x...) are generated by javascript-obfuscator > 1 | const _0x26d700=_0x176d;function _0x1e3d(){const _0x4edcee=['from','join','5159HJXDuY','_valid','_env','rotate','fillRec
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.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. 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. 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.
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.