@pinggy/pinggy
Pinggy SDK for Nodejs
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): Used in install.cjs for native binary fetch/build via node-pre-gyp; standard pattern for this package. | ai | |
| phantom-deps | phantom-dep:tar | AI (phantom-deps): Used indirectly by node-pre-gyp packaging; stable false positive for this native binding package. | ai | |
| phantom-deps | phantom-dep:adm-zip | AI (phantom-deps): Used indirectly by node-pre-gyp packaging; stable false positive for this native binding package. | ai | |
| phantom-deps | phantom-dep:follow-redirects | AI (phantom-deps): Used indirectly by node-pre-gyp binary download; stable false positive for this native binding package. | ai | |
| install-scripts | install-script:install | AI (install-scripts): Standard node-pre-gyp prebuilt binary fetch for native addon; matches documented binary config in package.json. | ai | |
| phantom-deps | phantom-dep:node-gyp | AI (phantom-deps): Known implicit dependency for native addon builds; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@mapbox/node-pre-gyp | AI (phantom-deps): Referenced in scripts/binary config, not imported directly; standard native addon pattern. | ai | |
| phantom-deps | phantom-dep:shlex | AI (phantom-deps): Likely used in config or build tooling; stable false positive for this native addon package. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 0.4.7 | 3 / 17 | |
| 0.4.4 | 3 / 17 | |
| 0.4.3 | 3 / 17 | |
| 0.4.2 | 3 / 17 | |
| 0.4.1 | 3 / 17 | |
| 0.3.9 | 3 / 17 | |
| 0.3.8 | 3 / 17 | |
| 0.3.7 | 3 / 17 | |
| 0.3.6 | 3 / 17 | |
| 0.3.4 | 3 / 17 | |
| 0.3.2 | 3 / 17 | |
| 0.3.1 | 4 / 17 | |
| 0.2.13 | 4 / 17 | |
| 0.2.12 | 4 / 17 | |
| 0.2.10 | 4 / 17 | |
| 0.2.9 | 4 / 17 | |
| 0.2.8 | 4 / 17 | |
| 0.2.7 | 4 / 17 | |
| 0.2.4 | 4 / 17 | |
| 0.2.3 | 4 / 17 | |
| 0.2.2 | 4 / 17 | |
| 0.2.1 | 4 / 17 | |
| 0.1.10 | 4 / 17 | |
| 0.1.8 | 3 / 17 | |
| 0.1.6 | 3 / 17 | |
| 0.1.5 | 3 / 17 | |
| 0.1.3 | 5 / 12 |
v0.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.