filter-values
Filter an object values using glob patterns or with a `callback` function returns true.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): doowb is a long-standing, trusted npm publisher and known collaborator with jonschlinkert in the same ecosystem. This transition is a legitimate maintainer handoff. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): doowb (Brian Woodward) is a well-known co-maintainer in the jonschlinkert/Assemble ecosystem; addition is a legitimate handoff, not a takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by a maintainer handoff to a trusted collaborator with no code changes; consistent with routine ecosystem maintenance, not account takeover. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.4.1 | 2 / 3 | |
| 0.4.0 | 2 / 2 | |
| 0.3.0 | 2 / 2 | |
| 0.2.0 | 0 / 2 | |
| 0.1.0 | 2 / 2 |
v0.4.1
2 findingsThis version was published by a different npm account than previous versions on 2017-05-11. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.