@momsfriendlydevco/marshal
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:eval-usage | AI (semgrep): eval() is intentional for function deserialization in a marshaling library; stable pattern across versions. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.2.0 | 2 / 3 | |
| 2.1.4 | 2 / 3 | |
| 2.1.3 | 2 / 3 | |
| 2.1.2 | 2 / 3 | |
| 2.1.1 | 2 / 3 | |
| 2.1.0 | 2 / 3 |
v2.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.