@push.rocks/smartnetwork
A toolkit for network diagnostics including speed tests, port availability checks, and more.
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 | missing-githead | AI (provenance): Publish metadata gap, not a behavior signal; lossless has strong track record. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is first-party @push.rocks package, same maintainer ecosystem. | ai | |
| source-diff | obfuscated-file:dist_ts/smartnetwork.classes.publicip.js | AI (source-diff): Readable TS source, long lines only; not true obfuscation. | ai | |
| source-diff | obfuscated-file:dist_ts/smartnetwork.classes.domainintelligence.js | AI (source-diff): Readable TS source, long lines only; not true obfuscation. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Cross-compiled rustnetwork binaries match new tsrust build tooling for this package's stated function. | ai | |
| source-diff | obfuscated-file:dist_ts/smartnetwork.classes.rustbridge.js | AI (source-diff): Readable TS source, long lines only; not true obfuscation. | ai | |
| source-diff | obfuscated-file:dist_ts/smartnetwork.classes.ipintelligence.js | AI (source-diff): Readable TS source, long lines only; not true obfuscation. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 4.10.0 | 4 / 5 | |
| 4.9.0 | 3 / 5 | |
| 4.8.0 | 3 / 5 | |
| 4.7.4 | 3 / 5 | |
| 4.7.3 | 3 / 5 | |
| 4.7.1 | 3 / 5 | |
| 4.7.0 | 3 / 5 | |
| 4.6.0 | 3 / 5 | |
| 4.5.2 | 3 / 5 | |
| 4.5.1 | 3 / 5 | |
| 4.5.0 | 3 / 5 | |
| 4.4.0 | 6 / 5 | |
| 4.3.0 | 6 / 5 | |
| 4.2.0 | 5 / 5 | |
| 4.1.2 | 7 / 5 | |
| 4.1.1 | 7 / 5 | |
| 4.1.0 | 7 / 5 | |
| 4.0.2 | 7 / 5 | |
| 4.0.1 | 7 / 6 | |
| 4.0.0 | 7 / 6 |
v4.10.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: lossless.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: lossless.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.0
6 findingsPackage contains compiled binaries that could be backdoors: • dist_rust/rustnetwork_linux_amd64 • dist_rust/rustnetwork_linux_arm64
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.