@nocobase/plugin-workflow
A powerful BPM tool that provides foundational support for business automation, with the capability to extend unlimited triggers and nodes.
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:dist/client/626.2d5a22c1f90a3ac8.js | AI (source-diff): Standard webpack bundle output for NocoBase client plugin; minification is expected across all versions. | ai | |
| source-diff | obfuscated-file:dist/client/f8056df738a9f579.js | AI (source-diff): Standard webpack-minified client bundle with NocoBase copyright header; not obfuscated malware. Expected output for this frontend plugin. | ai | |
| source-diff | obfuscated-file:dist/client/f4e6d701a7efef43.js | AI (source-diff): Standard webpack-minified client bundle with NocoBase copyright header; not obfuscated malware. Expected output for this frontend plugin. | ai | |
| source-diff | obfuscated-file:dist/client/70e9dec82e952acf.js | AI (source-diff): Standard webpack-minified client bundle with NocoBase copyright header; not obfuscated malware. Expected output for this frontend plugin. | ai | |
| source-diff | obfuscated-file:dist/client/c1b4661e7caee9c0.js | AI (source-diff): Standard webpack-minified client bundle with NocoBase copyright header and recognizable React/NocoBase code. Not obfuscated — minification is expected for this plugin's dist output. | ai | |
| source-diff | large-new-source-files | AI (source-diff): New source files are webpack build chunks for the client bundle. Normal for NocoBase plugin builds that split output into multiple chunks. | ai | |
| source-diff | obfuscated-file:dist/client/b41523353a3db32b.js | AI (source-diff): Standard webpack-minified client bundle with NocoBase copyright header and recognizable React/NocoBase code. Not obfuscated — minification is expected for this plugin's dist output. | ai | |
| source-diff | obfuscated-file:dist/client/73060898163a8aaa.js | AI (source-diff): Standard webpack-minified client bundle with NocoBase copyright header. Minified output is expected for this plugin's frontend dist; not actual obfuscation. | ai | |
| source-diff | obfuscated-file:dist/client/0e458d99e9fc5e65.js | AI (source-diff): Standard webpack-minified client bundle with NocoBase copyright header; recognizable React UI code, no malicious patterns. Expected build artifact for this plugin. | ai | |
| source-diff | obfuscated-file:dist/client/f39e94207f92e352.js | AI (source-diff): Standard webpack-minified frontend bundle for a React plugin; NocoBase ships minified client dist files in all versions. No malicious patterns present. | ai | |
| source-diff | obfuscated-file:dist/client/478692c1637f2742.js | AI (source-diff): Standard webpack-minified frontend bundle for a React plugin; NocoBase ships minified client dist files in all versions. No malicious patterns present. | ai | |
| source-diff | obfuscated-file:dist/client/c1347b9d21f864d9.js | AI (source-diff): Standard webpack-minified frontend bundle for a React plugin; NocoBase ships minified client dist files in all versions. No malicious patterns present. | ai | |
| source-diff | obfuscated-file:dist/client/27bd65abee87cafa.js | AI (source-diff): Standard webpack-minified frontend bundle for a React plugin; NocoBase ships minified client dist files in all versions. No malicious patterns present. | ai | |
| source-diff | obfuscated-file:dist/client/0f813db63cbc2726.js | AI (source-diff): Standard webpack-bundled client output with NocoBase copyright header; identical pattern to already-accepted sibling files. Normal for this frontend plugin package. | ai | |
| source-diff | obfuscated-file:dist/client/a738a283db5e13e7.js | AI (source-diff): NocoBase ships webpack-bundled client chunks as part of its standard build pipeline. Minified dist files with copyright headers are expected and not indicative of malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/client/10.dc2f9b83209e12b9.js | AI (source-diff): Standard webpack-minified client bundle with NocoBase copyright header; long lines are minification artifacts, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/client/781.d9277df85d1beaba.js | AI (source-diff): Standard webpack-minified client bundle with NocoBase copyright header; long lines are minification artifacts, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/client/771.5e7be8b4d4ac579f.js | AI (source-diff): Standard webpack-minified client bundle with NocoBase copyright header; long lines are minification artifacts, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/client/626.7d24ff2a47742f1b.js | AI (source-diff): Standard webpack-minified client bundle with NocoBase copyright header; long lines are minification artifacts, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/client/7d56e370959b89bb.js | AI (source-diff): Standard webpack-minified bundle with NocoBase copyright header and readable React/Ant Design UI code. Not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/client/2a8332e23037d42f.js | AI (source-diff): Standard webpack-minified bundle with NocoBase copyright header and readable React/Ant Design UI code. Not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/client/b6afdd7820bb1b71.js | AI (source-diff): Standard webpack-minified bundle with NocoBase copyright header and readable React/Ant Design UI code. Not malicious obfuscation. | ai | |
| bogus-package | bogus-package | AI (bogus-package): NocoBase plugin packages consistently use documentation-link READMEs pointing to their docs site. Not spam or phishing. | ai | |
| source-diff | obfuscated-file:dist/client/9e124936e3877c66.js | AI (source-diff): Standard webpack-minified bundle with NocoBase copyright header and readable React/Ant Design UI code. Not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/client/46ff6b84722c73a7.js | AI (source-diff): Standard webpack-minified client bundle for NocoBase plugin; copyright header and code structure confirm legitimate origin. Minification triggers the rule but poses no security risk. | ai |
Versions (showing 51 of 125)
| Version | Deps | Published |
|---|---|---|
| 2.0.61 | 0 / 18 | |
| 2.0.60 | 0 / 18 | |
| 2.0.59 | 0 / 18 | |
| 2.0.58 | 0 / 18 | |
| 2.0.57 | 0 / 18 | |
| 2.0.56 | 0 / 18 | |
| 2.0.55 | 0 / 18 | |
| 2.0.54 | 0 / 18 | |
| 2.0.53 | 0 / 18 | |
| 2.0.52 | 0 / 18 | |
| 2.0.51 | 0 / 18 | |
| 2.0.50 | 0 / 18 | |
| 2.0.49 | 0 / 18 | |
| 2.0.48 | 0 / 18 | |
| 2.0.47 | 0 / 18 | |
| 2.0.46 | 0 / 18 | |
| 2.0.45 | 0 / 18 | |
| 2.0.44 | 0 / 18 | |
| 2.0.43 | 0 / 18 | |
| 2.0.42 | 0 / 18 | |
| 2.0.41 | 0 / 18 | |
| 2.0.40 | 0 / 18 | |
| 2.0.39 | 0 / 18 | |
| 2.0.38 | 0 / 18 | |
| 2.0.37 | 0 / 18 | |
| 2.0.36 | 0 / 18 | |
| 2.0.35 | 0 / 18 | |
| 2.0.34 | 0 / 18 | |
| 2.0.33 | 0 / 18 | |
| 2.0.32 | 0 / 18 | |
| 2.0.31 | 0 / 18 | |
| 2.0.30 | 0 / 18 | |
| 2.0.29 | 0 / 18 | |
| 2.0.28 | 0 / 18 | |
| 2.0.27 | 0 / 18 | |
| 2.0.26 | 0 / 18 | |
| 2.0.25 | 0 / 18 | |
| 2.0.24 | 0 / 18 | |
| 2.0.23 | 0 / 18 | |
| 2.0.22 | 0 / 18 | |
| 2.0.21 | 0 / 18 | |
| 2.0.20 | 0 / 18 | |
| 2.0.19 | 0 / 18 | |
| 2.0.18 | 0 / 18 | |
| 2.0.17 | 0 / 18 | |
| 2.0.16 | 0 / 18 | |
| 2.0.15 | 0 / 18 | |
| 2.0.14 | 0 / 18 | |
| 2.0.13 | 0 / 18 | |
| 2.0.12 | 0 / 18 | |
| 2.0.11 | 0 / 18 |
v2.0.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.56
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.
v2.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.42
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.41
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.40
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.39
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.38
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.
v2.0.37
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.
v2.0.36
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.
v2.0.35
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.
v2.0.34
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.
v2.0.33
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.
v2.0.32
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.
v2.0.31
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.
v2.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.25
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.24
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.23
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.22
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.21
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.20
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.19
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.18
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.17
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.16
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.15
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.14
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.13
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.12
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.11
5 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.