@bobfrankston/iflow-direct
Direct IMAP client — transport-agnostic, no Node.js dependencies, browser-ready
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Absence of Sigstore provenance is common (~88% of packages) and not a security signal for this package. | ai |
Versions (showing 51 of 53)
| Version | Deps | Published |
|---|---|---|
| 0.1.58 | 1 / 1 | |
| 0.1.57 | 1 / 1 | |
| 0.1.56 | 1 / 1 | |
| 0.1.55 | 1 / 1 | |
| 0.1.54 | 1 / 1 | |
| 0.1.53 | 1 / 1 | |
| 0.1.52 | 1 / 1 | |
| 0.1.51 | 1 / 1 | |
| 0.1.50 | 1 / 1 | |
| 0.1.49 | 1 / 1 | |
| 0.1.48 | 1 / 1 | |
| 0.1.47 | 1 / 1 | |
| 0.1.46 | 1 / 1 | |
| 0.1.45 | 1 / 1 | |
| 0.1.44 | 1 / 1 | |
| 0.1.43 | 1 / 1 | |
| 0.1.42 | 1 / 1 | |
| 0.1.41 | 1 / 1 | |
| 0.1.40 | 1 / 1 | |
| 0.1.39 | 1 / 1 | |
| 0.1.35 | 1 / 1 | |
| 0.1.34 | 1 / 1 | |
| 0.1.33 | 1 / 1 | |
| 0.1.32 | 1 / 1 | |
| 0.1.31 | 1 / 1 | |
| 0.1.30 | 1 / 1 | |
| 0.1.28 | 1 / 1 | |
| 0.1.27 | 1 / 1 | |
| 0.1.26 | 1 / 1 | |
| 0.1.25 | 1 / 1 | |
| 0.1.24 | 1 / 1 | |
| 0.1.23 | 1 / 1 | |
| 0.1.22 | 1 / 1 | |
| 0.1.21 | 1 / 1 | |
| 0.1.20 | 1 / 0 | |
| 0.1.19 | 1 / 0 | |
| 0.1.18 | 1 / 0 | |
| 0.1.17 | 1 / 0 | |
| 0.1.16 | 1 / 0 | |
| 0.1.15 | 1 / 0 | |
| 0.1.13 | 0 / 0 | |
| 0.1.12 | 0 / 0 | |
| 0.1.11 | 0 / 0 | |
| 0.1.10 | 0 / 0 | |
| 0.1.9 | 0 / 0 | |
| 0.1.8 | 0 / 0 | |
| 0.1.7 | 0 / 0 | |
| 0.1.6 | 0 / 0 | |
| 0.1.5 | 0 / 0 | |
| 0.1.4 | 0 / 0 | |
| 0.1.3 | 0 / 0 |
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.