@blumintinc/flatten-anything
Flatten objects and replace nested props with 'prop.subprop'. A simple and small integration
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:filter-anything | AI (dependencies): filter-anything is a well-known mesqueeb utility; same ecosystem lineage as this package. | ai | |
| provenance | no-provenance | AI (provenance): Scoped fork of an established utility; no provenance is common and not a risk signal here. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 4.1.1 | 2 / 9 | |
| 4.1.0 | 2 / 9 | |
| 4.0.8 | 2 / 9 | |
| 4.0.7 | 2 / 9 | |
| 4.0.6 | 2 / 9 | |
| 4.0.5 | 2 / 9 | |
| 4.0.4 | 2 / 9 | |
| 4.0.3 | 2 / 9 |
v4.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.