@injectivelabs/test-utils
List of test-utils and helper functions that can be reused throughout Injective's projects.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:shx | AI (phantom-deps): Build tool dependency; used in build:post script, stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): Declared dependency; phantom-dep heuristic is false positive for utility library. | ai | |
| phantom-deps | phantom-dep:store2 | AI (phantom-deps): Declared dependency; phantom-dep heuristic is false positive for utility library. | ai | |
| phantom-deps | phantom-dep:bignumber.js | AI (phantom-deps): Declared dependency; phantom-dep heuristic is false positive for utility library. | ai | |
| phantom-deps | phantom-dep:snakecase-keys | AI (phantom-deps): Declared dependency; phantom-dep heuristic is false positive for utility library. | ai | |
| phantom-deps | phantom-dep:@injectivelabs/exceptions | AI (phantom-deps): Same-org scoped dependency; phantom-dep false positive for internal monorepo pattern. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.14.41 | 9 / 0 | |
| 1.14.40 | 9 / 0 | |
| 1.14.35 | 9 / 0 | |
| 1.14.33 | 9 / 0 | |
| 1.14.32 | 9 / 0 | |
| 1.14.30 | 9 / 0 | |
| 1.14.21 | 9 / 0 | |
| 1.14.20 | 9 / 0 | |
| 1.14.19 | 9 / 0 | |
| 1.14.17 | 9 / 0 | |
| 1.14.16 | 9 / 0 |
v1.14.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.