free-email-domains
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 |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): Long-standing postinstall on trusted high-download package; no malicious behavior in evidence. | ai |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 1.9.75 | 0 / 12 | |
| 1.9.74 | 0 / 12 | |
| 1.9.73 | 0 / 12 | |
| 1.9.58 | 0 / 12 | |
| 1.9.57 | 0 / 12 | |
| 1.9.56 | 0 / 12 | |
| 1.9.55 | 0 / 12 | |
| 1.9.54 | 0 / 12 | |
| 1.9.53 | 0 / 12 | |
| 1.9.52 | 0 / 12 | |
| 1.9.51 | 0 / 12 | |
| 1.9.50 | 0 / 12 | |
| 1.9.49 | 0 / 12 | |
| 1.9.48 | 0 / 12 | |
| 1.9.47 | 0 / 12 | |
| 1.9.46 | 0 / 12 | |
| 1.9.45 | 0 / 12 | |
| 1.9.44 | 0 / 12 | |
| 1.9.43 | 0 / 12 | |
| 1.9.42 | 0 / 12 | |
| 1.9.41 | 0 / 12 | |
| 1.9.40 | 0 / 12 | |
| 1.9.39 | 0 / 12 | |
| 1.9.38 | 0 / 12 | |
| 1.9.37 | 0 / 12 | |
| 1.9.36 | 0 / 12 | |
| 1.9.35 | 0 / 12 | |
| 1.9.34 | 0 / 12 | |
| 1.9.33 | 0 / 12 | |
| 1.9.32 | 0 / 12 | |
| 1.9.31 | 0 / 12 | |
| 1.9.30 | 0 / 12 | |
| 1.9.29 | 0 / 12 | |
| 1.9.28 | 0 / 12 | |
| 1.9.27 | 0 / 12 | |
| 1.9.26 | 0 / 12 | |
| 1.9.25 | 0 / 12 | |
| 1.9.24 | 0 / 12 | |
| 1.9.23 | 0 / 12 | |
| 1.9.22 | 0 / 12 | |
| 1.9.21 | 0 / 12 | |
| 1.9.20 | 0 / 12 | |
| 1.9.5 | 0 / 12 | |
| 1.9.4 | 0 / 12 | |
| 1.9.3 | 0 / 12 |
v1.9.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.58
2 findingsScript: node scripts/postinstall.mjs
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.57
2 findingsScript: node scripts/postinstall.mjs
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.56
2 findingsScript: node scripts/postinstall.mjs
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.55
2 findingsScript: node scripts/postinstall.mjs
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.54
2 findingsScript: node scripts/postinstall.mjs
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.53
2 findingsScript: node scripts/postinstall.mjs
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.52
2 findingsScript: node scripts/postinstall.mjs
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.51
2 findingsScript: node scripts/postinstall.mjs
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.50
2 findingsScript: node scripts/postinstall.mjs
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.49
2 findingsScript: node scripts/postinstall.mjs
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.