@moralisweb3/streams
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
locothedevernowcicdmoralisy0moocapplequoppegerardo15ivanontech
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Scoped monorepo sub-package; missing README/repo metadata is a known pattern for internal Moralis packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Same monorepo pattern; description lives in the moralis metadata field, not the top-level description. | ai | |
| phantom-deps | phantom-dep:web3-eth-abi | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic may miss indirect usage in bundled output. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 2.27.2 | 11 / 11 |
v2.27.2
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.