@layerzerolabs/protocol-stellar-v2
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
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 0.2.101 | 0 / 6 | |
| 0.2.99 | 0 / 6 | |
| 0.2.98 | 0 / 6 | |
| 0.2.97 | 0 / 6 | |
| 0.2.96 | 0 / 6 | |
| 0.2.95 | 0 / 6 | |
| 0.2.94 | 0 / 6 | |
| 0.2.93 | 0 / 6 | |
| 0.2.92 | 0 / 6 | |
| 0.2.91 | 0 / 6 | |
| 0.2.90 | 0 / 6 | |
| 0.2.89 | 0 / 6 | |
| 0.2.88 | 0 / 6 | |
| 0.2.87 | 0 / 6 | |
| 0.2.86 | 0 / 6 | |
| 0.2.85 | 0 / 6 | |
| 0.2.84 | 0 / 6 | |
| 0.2.83 | 0 / 6 | |
| 0.2.82 | 0 / 6 | |
| 0.2.62 | 0 / 6 | |
| 0.2.10 | 0 / 5 | |
| 0.2.9 | 0 / 5 | |
| 0.2.8 | 0 / 5 |
v0.2.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.99
28 findingsModified file contains 42 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 72 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 27 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 82 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 83 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 54 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 53 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 84 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 68 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 104 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 39 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 34 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 49 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 56 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 83 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 17 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.62
33 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.
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.
Modified file contains 42 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 72 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 83 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 49 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 83 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
6 findingsModified file contains 29 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 36 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 63 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 29 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 61 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.