@bobfrankston/mailx-imap
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Consistent across all versions of this package; not indicative of malice given publisher track record. | ai | |
| provenance | no-provenance | AI (provenance): Publisher has 168 approved packages, none with provenance; stable pattern for this ecosystem. | ai |
Versions (showing 51 of 118)
| Version | Deps | Published |
|---|---|---|
| 0.1.133 | 8 / 0 | |
| 0.1.131 | 8 / 0 | |
| 0.1.130 | 8 / 0 | |
| 0.1.129 | 8 / 0 | |
| 0.1.128 | 8 / 0 | |
| 0.1.126 | 8 / 0 | |
| 0.1.125 | 8 / 0 | |
| 0.1.124 | 8 / 0 | |
| 0.1.122 | 8 / 0 | |
| 0.1.121 | 8 / 0 | |
| 0.1.120 | 8 / 0 | |
| 0.1.119 | 8 / 0 | |
| 0.1.118 | 8 / 0 | |
| 0.1.117 | 8 / 0 | |
| 0.1.116 | 8 / 0 | |
| 0.1.115 | 8 / 0 | |
| 0.1.114 | 8 / 0 | |
| 0.1.113 | 8 / 0 | |
| 0.1.112 | 8 / 0 | |
| 0.1.111 | 8 / 0 | |
| 0.1.110 | 8 / 0 | |
| 0.1.109 | 8 / 0 | |
| 0.1.108 | 8 / 0 | |
| 0.1.106 | 8 / 0 | |
| 0.1.105 | 8 / 0 | |
| 0.1.104 | 8 / 0 | |
| 0.1.103 | 8 / 0 | |
| 0.1.102 | 8 / 0 | |
| 0.1.100 | 8 / 0 | |
| 0.1.99 | 8 / 0 | |
| 0.1.98 | 8 / 0 | |
| 0.1.97 | 8 / 0 | |
| 0.1.96 | 8 / 0 | |
| 0.1.95 | 8 / 0 | |
| 0.1.94 | 8 / 0 | |
| 0.1.93 | 8 / 0 | |
| 0.1.92 | 8 / 0 | |
| 0.1.91 | 8 / 0 | |
| 0.1.90 | 8 / 0 | |
| 0.1.89 | 8 / 0 | |
| 0.1.88 | 8 / 0 | |
| 0.1.87 | 8 / 0 | |
| 0.1.86 | 8 / 0 | |
| 0.1.85 | 8 / 0 | |
| 0.1.84 | 8 / 0 | |
| 0.1.83 | 8 / 0 | |
| 0.1.82 | 8 / 0 | |
| 0.1.81 | 8 / 0 | |
| 0.1.80 | 8 / 0 | |
| 0.1.79 | 8 / 0 | |
| 0.1.78 | 8 / 0 |
v0.1.133
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.131
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.130
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.129
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.128
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.126
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.125
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.124
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.122
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.121
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.120
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.119
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.118
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.117
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.116
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.115
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.114
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.113
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.112
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.111
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.110
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.