@openfn/compiler
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): jclark-openfn is an established @openfn org publisher with 137 approved packages; transition appears legitimate. | ai | |
| provenance | no-provenance | AI (provenance): Established OpenFn org package; lack of provenance is consistent across all versions and not a risk indicator here. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.2.5 | 6 / 7 | |
| 1.2.4 | 6 / 7 | |
| 1.2.3 | 6 / 7 | |
| 1.2.2 | 6 / 7 | |
| 1.2.1 | 6 / 7 | |
| 1.2.0 | 6 / 7 | |
| 1.1.5 | 6 / 7 | |
| 1.1.4 | 6 / 7 | |
| 1.1.3 | 6 / 7 | |
| 1.1.2 | 6 / 7 | |
| 1.1.1 | 6 / 7 | |
| 1.1.0 | 6 / 7 | |
| 1.0.4 | 6 / 7 | |
| 1.0.3 | 6 / 7 | |
| 1.0.2 | 6 / 7 | |
| 1.0.1 | 6 / 7 | |
| 1.0.0 | 6 / 7 |
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.