@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, 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 |
|---|---|---|---|---|
| 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 51 of 69)
| 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 | |
| 0.1.48 | 5 / 3 | |
| 0.1.47 | 5 / 3 | |
| 0.1.46 | 5 / 3 | |
| 0.1.45 | 5 / 3 | |
| 0.1.44 | 5 / 3 | |
| 0.1.43 | 5 / 3 | |
| 0.1.42 | 5 / 3 | |
| 0.1.41 | 5 / 3 | |
| 0.1.40 | 5 / 3 | |
| 0.1.39 | 5 / 3 | |
| 0.1.38 | 5 / 3 | |
| 0.1.37 | 5 / 3 | |
| 0.1.36 | 5 / 3 | |
| 0.1.35 | 5 / 3 | |
| 0.1.34 | 5 / 3 | |
| 0.1.33 | 5 / 3 | |
| 0.1.32 | 5 / 3 | |
| 0.1.31 | 5 / 3 | |
| 0.1.30 | 5 / 3 | |
| 0.1.29 | 5 / 3 | |
| 0.1.28 | 5 / 3 | |
| 0.1.27 | 5 / 3 | |
| 0.1.26 | 5 / 3 | |
| 0.1.25 | 5 / 3 | |
| 0.1.24 | 5 / 3 | |
| 0.1.23 | 5 / 3 | |
| 0.1.22 | 5 / 3 | |
| 0.1.21 | 5 / 3 |
v0.1.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.29
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.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.23
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (aniket-engg) than the most recent previously approved version (yann300) on 2024-02-27, but aniket-engg is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.1.22
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (yann300) than the most recent previously approved version (aniket-engg) on 2024-02-14, but yann300 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.1.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.