merge-defaults
A recursive version of _.defaults.
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Package is 12+ years old with 7 versions and 17 approved dependents. The 0.0.0 version is a historical artifact from a trusted publisher, not a malicious indicator. | ai | |
| provenance | publisher-changed | AI (provenance): rachaelshaw is a known Sails.js core team member; transition from balderdashy (Sails.js org account) is a legitimate intra-org handoff, not a takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @sailshq/lodash is the Sails.js org's own lodash fork, a well-known benign substitution across the Sails.js ecosystem. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.2.2 | 1 / 2 | |
| 0.2.1 | 1 / 2 | |
| 0.2.0 | 1 / 2 | |
| 0.1.4 | 1 / 2 | |
| 0.1.3 | 1 / 1 | |
| 0.1.0 | 1 / 1 | |
| 0.0.0 | 0 / 0 |
v0.2.2
2 findingsThis version was published by a different npm account than previous versions on 2019-04-30. 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.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.