@moralisweb3/common-sol-utils
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
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): Moralis SDK monorepo sub-package; sparse metadata is a consistent pattern across all its scoped packages, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Moralis monorepo sub-packages consistently omit top-level description; not a risk signal for this package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 2.27.2 | 4 / 10 | |
| 2.27.1 | 4 / 10 | |
| 2.27.0 | 4 / 10 | |
| 2.26.9 | 4 / 10 | |
| 2.26.8 | 4 / 10 | |
| 2.26.7 | 4 / 10 | |
| 2.26.6 | 4 / 10 | |
| 2.26.5 | 4 / 10 | |
| 2.26.4 | 4 / 10 | |
| 2.26.3 | 4 / 10 | |
| 2.26.2 | 4 / 10 |
v2.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.