@balancy/core
todo
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Same-org maintainer transition, consistent with local build script paths referencing pavel's own machine. | ai | |
| source-diff | obfuscated-file:dist/webview/balancy-webview.es.js | AI (source-diff): Minified vite bundle for webview UI, not true obfuscation; no malicious behavior in sample. | ai | |
| source-diff | net-exec-file:dist/webview/balancy-webview.es.js | AI (source-diff): Iframe/DOM utility code from bundler output, no exfil or dropper behavior observed. | ai | |
| source-diff | net-exec-file:dist/webview/balancy-webview.umd.js | AI (source-diff): Same bundled webview code as .es.js variant, benign UMD build. | ai | |
| phantom-deps | phantom-dep:jszip | AI (phantom-deps): jszip is a declared runtime dependency of this SDK; phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:@types/jszip | AI (phantom-deps): Type declaration package for jszip; loaded by convention, not a real phantom dep. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @balancy/core is a scoped gamedev SDK, not a typosquat of cors; name similarity is coincidental. | ai |
Versions (showing 51 of 86)
| Version | Deps | Published |
|---|---|---|
| 1.6.21 | 5 / 0 | |
| 1.6.11 | 5 / 0 | |
| 1.6.10 | 5 / 0 | |
| 1.6.9 | 5 / 0 | |
| 1.6.8 | 5 / 0 | |
| 1.6.7 | 5 / 0 | |
| 1.6.6 | 5 / 0 | |
| 1.6.5 | 5 / 0 | |
| 1.4.5 | 5 / 0 | |
| 1.4.4 | 5 / 0 | |
| 1.4.3 | 5 / 0 | |
| 1.3.6 | 5 / 0 | |
| 1.3.5 | 5 / 0 | |
| 1.3.4 | 5 / 0 | |
| 1.3.3 | 5 / 0 | |
| 1.3.2 | 5 / 0 | |
| 1.2.6 | 5 / 0 | |
| 1.2.5 | 5 / 0 | |
| 1.2.4 | 5 / 0 | |
| 1.2.3 | 5 / 0 | |
| 1.2.2 | 5 / 0 | |
| 1.2.1 | 5 / 0 | |
| 1.2.0 | 5 / 0 | |
| 1.1.47 | 5 / 0 | |
| 1.1.37 | 5 / 0 | |
| 1.1.36 | 5 / 0 | |
| 1.1.34 | 5 / 0 | |
| 1.1.33 | 5 / 0 | |
| 1.1.31 | 5 / 0 | |
| 1.1.29 | 5 / 0 | |
| 1.1.28 | 5 / 0 | |
| 1.1.27 | 5 / 0 | |
| 1.1.22 | 5 / 0 | |
| 1.1.20 | 5 / 0 | |
| 1.1.19 | 5 / 0 | |
| 1.1.18 | 5 / 0 | |
| 1.1.17 | 5 / 0 | |
| 1.1.16 | 5 / 0 | |
| 1.1.15 | 5 / 0 | |
| 1.1.12 | 5 / 0 | |
| 1.1.11 | 5 / 0 | |
| 1.1.10 | 5 / 0 | |
| 1.1.8 | 5 / 0 | |
| 1.1.7 | 5 / 0 | |
| 1.1.6 | 5 / 0 | |
| 1.1.5 | 5 / 0 | |
| 1.0.46 | 5 / 0 | |
| 1.0.45 | 5 / 0 | |
| 1.0.44 | 5 / 0 | |
| 1.0.43 | 5 / 0 | |
| 1.0.42 | 5 / 0 |
v1.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.5
5 findingsThis version was published by a different npm account than previous versions on 2026-03-17. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
2 findingsThis version was published by a different npm account than previous versions on 2026-03-14. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
2 findingsThis version was published by a different npm account than previous versions on 2026-03-13. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
2 findingsThis version was published by a different npm account than previous versions on 2026-03-03. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
2 findingsThis version was published by a different npm account than previous versions on 2026-03-02. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
2 findingsThis version was published by a different npm account than previous versions on 2026-03-02. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
2 findingsThis version was published by a different npm account than previous versions on 2026-03-02. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
2 findingsThis version was published by a different npm account than previous versions on 2026-02-24. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
2 findingsThis version was published by a different npm account than previous versions on 2026-02-13. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
2 findingsThis version was published by a different npm account than previous versions on 2026-02-12. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
2 findingsThis version was published by a different npm account than previous versions on 2026-02-10. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
2 findingsThis version was published by a different npm account than previous versions on 2026-01-26. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
2 findingsThis version was published by a different npm account than previous versions on 2026-01-23. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
2 findingsThis version was published by a different npm account than previous versions on 2026-01-16. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-10. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.47
2 findingsThis version was published by a different npm account than previous versions on 2026-01-08. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.