penpal
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 |
|---|---|---|---|---|
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get used for legitimate proxy-based RPC forwarding, core to penpal's design. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 7.0.6 | 0 / 30 | |
| 7.0.5 | 0 / 30 | |
| 7.0.4 | 0 / 30 | |
| 7.0.3 | 0 / 30 | |
| 7.0.2 | 0 / 30 | |
| 7.0.1 | 0 / 30 | |
| 7.0.0 | 0 / 29 |
v7.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.