@injectivelabs/exceptions
List of exceptions that 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 | publisher-changed | AI (provenance): InjectiveLabs migrated to GitHub Actions CI publishing with SLSA attestation; stable pattern going forward. | ai | |
| provenance | missing-githead | AI (provenance): GitHub Actions CI publish pipeline doesn't inject gitHead; SLSA attestation provides stronger provenance. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with org-level CI migration; no malicious indicators present. | ai |
Versions (showing 45 of 152)
| Version | Deps | Published |
|---|---|---|
| 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.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.11 | 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 |
v1.16.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.