@remix-project/ghaction-helper
Solidity Tests GitHub Action Helper
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has 47 approved packages and no rejections; repo matches ethereum/remix-project org; no code changes introduced. | ai | |
| dependencies | unvetted-dep:@ethereum-waffle/chai | AI (dependencies): @ethereum-waffle/chai is a well-known Ethereum testing library; stable dependency for this package. | ai | |
| provenance | no-provenance | AI (provenance): Remix-project org packages consistently lack provenance; stable false positive for this package family. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 0.1.71 | 4 / 3 | |
| 0.1.70 | 4 / 3 | |
| 0.1.69 | 4 / 3 | |
| 0.1.68 | 4 / 3 | |
| 0.1.67 | 4 / 3 | |
| 0.1.66 | 4 / 3 | |
| 0.1.65 | 4 / 3 | |
| 0.1.64 | 4 / 3 | |
| 0.1.63 | 4 / 3 | |
| 0.1.62 | 4 / 3 | |
| 0.1.61 | 4 / 3 | |
| 0.1.60 | 5 / 3 | |
| 0.1.59 | 5 / 3 | |
| 0.1.58 | 5 / 3 | |
| 0.1.57 | 5 / 3 | |
| 0.1.56 | 5 / 3 | |
| 0.1.55 | 5 / 3 | |
| 0.1.54 | 5 / 3 | |
| 0.1.53 | 5 / 3 | |
| 0.1.52 | 5 / 3 | |
| 0.1.51 | 5 / 3 | |
| 0.1.50 | 5 / 3 | |
| 0.1.49 | 5 / 3 |
v0.1.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.