@injectivelabs/networks
Endpoints, networks, etc. Can be reused throughout Injective's projects.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): CI/CD migration to GitHub Actions with SLSA attestation explains missing gitHead; stable pattern for this org going forward. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing with SLSA provenance is a legitimate and stronger supply chain practice. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer consolidation consistent with org-level CI/CD migration; no malicious indicators present. | ai |
Versions (showing 84 of 184)
| Version | Deps | Published |
|---|---|---|
| 1.16.26 | 1 / 1 | |
| 1.16.25 | 1 / 1 | |
| 1.16.24 | 1 / 1 | |
| 1.16.23 | 1 / 1 | |
| 1.16.22 | 1 / 1 | |
| 1.16.21 | 1 / 1 | |
| 1.16.20 | 1 / 1 | |
| 1.16.19 | 1 / 1 | |
| 1.16.18 | 1 / 1 | |
| 1.16.17 | 1 / 1 | |
| 1.16.16 | 1 / 1 | |
| 1.16.15 | 1 / 1 | |
| 1.16.14 | 1 / 1 | |
| 1.16.13 | 1 / 1 | |
| 1.16.12 | 1 / 1 | |
| 1.16.11 | 1 / 1 | |
| 1.16.10 | 1 / 1 | |
| 1.16.9 | 1 / 1 | |
| 1.16.8 | 1 / 1 | |
| 1.16.7 | 1 / 1 | |
| 1.16.6 | 1 / 1 | |
| 1.16.5 | 1 / 1 | |
| 1.16.4 | 1 / 1 | |
| 1.16.3 | 1 / 1 | |
| 1.16.2 | 1 / 1 | |
| 1.16.1 | 1 / 1 | |
| 1.15.41 | 1 / 1 | |
| 1.15.40 | 1 / 1 | |
| 1.15.39 | 1 / 1 | |
| 1.15.38 | 1 / 1 | |
| 1.15.37 | 1 / 1 | |
| 1.15.36 | 1 / 1 | |
| 1.15.35 | 1 / 1 | |
| 1.15.34 | 1 / 1 | |
| 1.15.33 | 1 / 1 | |
| 1.15.32 | 1 / 1 | |
| 1.15.31 | 1 / 1 | |
| 1.15.30 | 1 / 1 | |
| 1.15.29 | 1 / 1 | |
| 1.15.28 | 1 / 1 | |
| 1.15.27 | 1 / 1 | |
| 1.15.26 | 1 / 1 | |
| 1.15.25 | 1 / 1 | |
| 1.15.24 | 1 / 1 | |
| 1.15.23 | 1 / 1 | |
| 1.15.22 | 1 / 1 | |
| 1.15.21 | 1 / 1 | |
| 1.15.20 | 1 / 1 | |
| 1.15.19 | 1 / 1 | |
| 1.15.18 | 1 / 1 | |
| 1.15.17 | 1 / 1 | |
| 1.15.16 | 1 / 1 | |
| 1.15.15 | 1 / 1 | |
| 1.15.14 | 1 / 1 | |
| 1.15.13 | 1 / 1 | |
| 1.15.12 | 1 / 1 | |
| 1.15.10 | 1 / 1 | |
| 1.15.9 | 1 / 1 | |
| 1.15.8 | 1 / 1 | |
| 1.15.7 | 1 / 1 | |
| 1.15.6 | 1 / 1 | |
| 1.15.5 | 1 / 1 | |
| 1.15.4 | 1 / 1 | |
| 1.15.3 | 1 / 1 | |
| 1.15.2 | 1 / 1 | |
| 1.15.1 | 1 / 1 | |
| 1.15.0 | 1 / 1 | |
| 1.14.47 | 1 / 1 | |
| 1.14.46 | 1 / 1 | |
| 1.14.45 | 1 / 1 | |
| 1.14.44 | 1 / 1 | |
| 1.14.43 | 1 / 1 | |
| 1.14.41 | 4 / 0 | |
| 1.14.40 | 4 / 0 | |
| 1.14.35 | 4 / 0 | |
| 1.14.33 | 4 / 0 | |
| 1.14.32 | 4 / 0 | |
| 1.14.30 | 4 / 0 | |
| 1.14.21 | 4 / 0 | |
| 1.14.20 | 4 / 0 | |
| 1.14.19 | 4 / 0 | |
| 1.14.18 | 4 / 0 | |
| 1.14.17 | 4 / 0 | |
| 1.14.16 | 4 / 0 |
v1.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.