@synnaxlabs/x
Common Utilities for Synnax Labs
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 | obfuscated-file:dist/scale-Bzn1Cl0r.cjs | AI (source-diff): Standard Vite/Rollup minified CJS chunk; content is readable scale/transform utility code. | ai | |
| source-diff | obfuscated-file:dist/box-BcGdqkt4.cjs | AI (source-diff): Standard Vite/Rollup minified CJS chunk; content is readable spatial utility code. | ai | |
| source-diff | obfuscated-file:dist/series-anlpaR_I.cjs | AI (source-diff): Standard Vite/Rollup minified CJS chunk; content is readable time-series utility code. | ai | |
| source-diff | obfuscated-file:dist/series-CcA_WjbJ.cjs | AI (source-diff): Standard Vite/Rollup minified CJS chunk; content is readable time-series/timestamp logic. | ai | |
| source-diff | obfuscated-file:dist/xy-DWwtHmgn.cjs | AI (source-diff): Standard Vite/Rollup minified CJS chunk; content matches declared xy/spatial utilities. | ai | |
| source-diff | obfuscated-file:dist/series-C6ZwNf8i.cjs | AI (source-diff): Standard Vite/Rollup minified CJS chunk; content matches declared telem/series utilities. | ai | |
| source-diff | obfuscated-file:dist/scale-BHs716im.cjs | AI (source-diff): Standard Vite/Rollup minified CJS chunk; content matches declared scale utilities. | ai | |
| source-diff | obfuscated-file:dist/box-Blu-4d1n.cjs | AI (source-diff): Standard Vite/Rollup minified CJS chunk; content matches declared box/spatial utilities. | ai | |
| source-diff | obfuscated-file:dist/bounds-BXbqBINt.cjs | AI (source-diff): Standard Vite/Rollup minified CJS chunk; readable domain logic, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/xy-BKIJiLu_.cjs | AI (source-diff): Standard Vite/Rollup minified CJS chunk; readable domain logic, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/series-tAhThbnz.cjs | AI (source-diff): Standard Vite/Rollup minified CJS chunk; readable domain logic, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/scale-76Azh2EE.cjs | AI (source-diff): Standard Vite/Rollup minified CJS chunk; readable domain logic, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/box-qgxWXNhm.cjs | AI (source-diff): Standard Vite/Rollup minified CJS chunk; readable domain logic, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/series-B2zqvP8A.cjs | AI (source-diff): Standard Vite/Rollup minified CJS chunk; content is time-series/telemetry utilities with no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/bounds-C2TKFgVk.cjs | AI (source-diff): Standard Vite/Rollup minified CJS chunk; content is spatial math utilities with no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/box-rH3ggwXk.cjs | AI (source-diff): Standard Vite/Rollup minified CJS chunk; content is box/spatial utilities with no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/scale-BXy1w8R_.cjs | AI (source-diff): Standard Vite/Rollup minified CJS chunk; content is scale/transform utilities with no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/xy-C-MUIjVs.cjs | AI (source-diff): Standard Vite/Rollup minified CJS chunk; content is XY coordinate utilities with no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/scale-C3fEtXxW.cjs | AI (source-diff): Standard Vite/Rollup minified CJS chunk; content is readable scale utility code. | ai | |
| source-diff | obfuscated-file:dist/bounds-CRK04jp7.cjs | AI (source-diff): Standard Vite/Rollup minified CJS chunk; content is readable utility code, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/series-BcF7A8Je.cjs | AI (source-diff): Standard Vite/Rollup minified CJS chunk; content is readable series/time utility code. | ai | |
| source-diff | obfuscated-file:dist/scale-C6qKDbRb.cjs | AI (source-diff): Standard Vite/Rollup minified CJS chunk; content is legitimate scale utility code. | ai | |
| source-diff | obfuscated-file:dist/box-Cxki783Y.cjs | AI (source-diff): Standard Vite/Rollup minified CJS chunk; content is legitimate spatial utility code. | ai | |
| source-diff | obfuscated-file:dist/bounds-D6e9xoHt.cjs | AI (source-diff): Standard Vite/Rollup minified CJS chunk; content is legitimate utility code, not obfuscation. | ai | |
| phantom-deps | phantom-dep:@msgpack/msgpack | AI (phantom-deps): @msgpack/msgpack is declared in package.json dependencies and used in binary serialization; heuristic false positive. | ai | |
| source-diff | obfuscated-file:dist/series-CYAhDD6B.cjs | AI (source-diff): Standard Vite/Rollup minified CJS chunk; content is legitimate series/time utility code. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation is a legitimate supply chain improvement for this org. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @synnaxlabs/x; Levenshtein match to 'qs' is a false positive with no brand similarity. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() appears in a benchmark test file (set.bench.ts) as a standard Proxy handler pattern, not obfuscation. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @synnaxlabs/x; Levenshtein match to 'pg' is a false positive with no brand similarity. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 0.56.1 | 4 / 10 | |
| 0.56.0 | 4 / 10 | |
| 0.55.0 | 4 / 10 | |
| 0.54.2 | 4 / 10 | |
| 0.54.1 | 4 / 10 | |
| 0.54.0 | 4 / 10 | |
| 0.53.1 | 4 / 10 | |
| 0.53.0 | 4 / 10 | |
| 0.52.5 | 4 / 10 | |
| 0.52.4 | 4 / 10 | |
| 0.52.3 | 4 / 10 | |
| 0.50.0 | 4 / 10 | |
| 0.49.3 | 4 / 10 | |
| 0.49.2 | 4 / 10 | |
| 0.49.0 | 4 / 10 | |
| 0.48.0 | 5 / 10 | |
| 0.47.0 | 5 / 10 | |
| 0.46.2 | 5 / 10 | |
| 0.46.1 | 5 / 10 | |
| 0.46.0 | 5 / 10 | |
| 0.45.1 | 5 / 10 | |
| 0.45.0 | 5 / 10 | |
| 0.44.4 | 5 / 10 | |
| 0.44.3 | 5 / 10 | |
| 0.44.2 | 5 / 10 | |
| 0.44.1 | 5 / 10 | |
| 0.44.0 | 5 / 10 | |
| 0.43.0 | 5 / 10 | |
| 0.42.3 | 4 / 10 | |
| 0.42.1 | 4 / 10 | |
| 0.42.0 | 4 / 10 |
v0.56.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.56.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.55.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.53.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-19. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.53.0
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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.52.5
2 findingsThis version was published by a different npm account than previous versions on 2026-03-10. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.52.4
2 findingsThis version was published by a different npm account than previous versions on 2026-03-06. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.52.3
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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.50.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.2
6 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.1
6 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.0
6 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.1
6 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.0
6 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.4
6 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.3
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.
v0.44.2
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.
v0.44.1
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.
v0.44.0
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.
v0.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.