anchor — Greenflagged

High-level validation library for Node.js (used in Waterline)

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

particlebananasgress454balderdashymikermcneileashaw

Keywords

validationrecursive-validatornestedvalidatorstrict-typesweb-frameworktype-coercionwaterlinevalidate-parameterssails.jssails

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	no-provenance	AI (provenance): Package predates Sigstore provenance by many years; absence of attestation is expected and not a risk signal for this package.	ai	2026/04/24
source-diff	net-exec-file:node_modules/lodash/lodash.js	AI (source-diff): Standard Lo-Dash 2.4.1 library file. Uses Function constructor for template compilation and AMD/CommonJS exports — not malware. False positive for this well-known utility library.	ai	2026/04/24
source-diff	net-exec-file:node_modules/lodash/dist/lodash.compat.js	AI (source-diff): Standard Lo-Dash 2.4.1 compat build. Same pattern as main lodash.js — legitimate utility library, not malware.	ai	2026/04/24
source-diff	net-exec-file:node_modules/lodash/dist/lodash.js	AI (source-diff): Standard Lo-Dash 2.4.1 modern build. Legitimate utility library bundled as dependency.	ai	2026/04/24
source-diff	net-exec-file:node_modules/lodash/dist/lodash.underscore.js	AI (source-diff): Standard Lo-Dash 2.4.1 underscore-compatible build. Legitimate utility library bundled as dependency.	ai	2026/04/24
npm-metadata	suspicious-initial-version	AI (npm-metadata): Version 0.0.0 is a legitimate pre-release placeholder from balderdashy (Sails.js), a well-established publisher. Not indicative of malicious intent.	ai	2026/04/24
bogus-package	bogus-package	AI (bogus-package): Package is an explicitly unreleased stub from a trusted publisher (balderdashy). Minimal content and no deps are expected for this type of placeholder.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): eashaw is a known, trusted Sails.js ecosystem contributor; maintainer addition reflects legitimate team transition, not a takeover.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): eashaw is a well-established Sails.js ecosystem publisher (848 approved packages) taking over from mikermcneil; consistent with legitimate org-level maintainer transition.	ai	2026/04/24

Versions (showing 42 of 42)

Version	Deps	Published
1.4.2	2 / 2	2025-11-21
1.4.1	2 / 2	2022-08-22
1.4.0	2 / 2	2018-12-17
1.3.0	2 / 2	2018-04-01
1.2.1	2 / 2	2018-04-01
1.2.0	2 / 2	2017-10-20
1.1.2	2 / 2	2017-09-24
1.1.1	2 / 2	2016-12-22
1.1.0	2 / 2	2016-12-22
1.0.0	2 / 2	2016-12-21
0.11.6	3 / 2	2017-08-08
0.11.5	3 / 2	2016-12-05
0.11.4	3 / 2	2016-12-05
0.11.3	3 / 2	2016-10-25
0.11.2	3 / 2	2016-03-17
0.11.1	3 / 2	2016-03-12
0.11.0	3 / 2	2015-12-28
0.10.4	3 / 2	2015-07-08
0.10.3	3 / 2	2015-06-09
0.10.2	2 / 2	2014-11-21
0.10.1	2 / 2	2014-09-25
0.9.13	3 / 1	2014-06-20
0.9.12	3 / 1	2014-03-03
0.9.11	3 / 1	2014-02-28
0.9.10	3 / 1	2014-02-27
0.9.9	3 / 1	2014-02-26
0.9.8	3 / 1	2014-02-25
0.9.7	3 / 1	2013-12-20
0.9.6	3 / 0	2013-10-29
0.9.5	3 / 0	2013-09-17
0.9.4	3 / 0	2013-09-04
0.9.3	3 / 0	2013-08-21
0.9.2	3 / 0	2013-08-09
0.9.1	3 / 0	2013-07-30
0.9.0	3 / 0	2013-07-18
0.4.1	3 / 0	2013-06-27
0.4.0	3 / 0	2013-06-25
0.3.0	3 / 0	2013-03-16
0.2.1	3 / 0	2013-03-12
0.2.0	2 / 0	2013-03-12
0.1.0	2 / 0	2013-01-21
0.0.0	0 / 0	2012-12-26

v1.4.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.1

2 findings

HIGH Publisher changed: mikermcneil → eashaw (on 2022-08-22) provenance

This version was published by a different npm account than previous versions on 2022-08-22. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.1

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: sgress454 → mikermcneil (on 2018-04-01) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-04-01. This could indicate a legitimate maintainer transition or an account compromise.

v1.2.0

2 findings

HIGH Publisher changed: mikermcneil → sgress454 (on 2017-10-20) provenance

This version was published by a different npm account than previous versions on 2017-10-20. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.2

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: sgress454 → mikermcneil (on 2017-09-24) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2017-09-24. This could indicate a legitimate maintainer transition or an account compromise.

v1.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.3

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: particlebanana → sgress454 (on 2016-10-25) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-10-25. This could indicate a legitimate maintainer transition or an account compromise.

v0.11.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.1

6 findings

HIGH New file with network + code execution: node_modules/lodash/lodash.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: node_modules/lodash/dist/lodash.compat.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: node_modules/lodash/dist/lodash.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: node_modules/lodash/dist/lodash.underscore.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: particlebanana → mikermcneil (on 2016-03-12) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-03-12. This could indicate a legitimate maintainer transition or an account compromise.

v0.11.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.2

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: sgress454 → particlebanana (on 2014-11-21) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2014-11-21. This could indicate a legitimate maintainer transition or an account compromise.

v0.10.1

2 findings

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: balderdashy → sgress454 (on 2014-09-25) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2014-09-25. This could indicate a legitimate maintainer transition or an account compromise.

v0.9.13

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: particlebanana → balderdashy (on 2014-06-20) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2014-06-20. This could indicate a legitimate maintainer transition or an account compromise.

v0.9.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.11

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.9

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.2

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: balderdashy → particlebanana (on 2013-08-09) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2013-08-09. This could indicate a legitimate maintainer transition or an account compromise.

v0.9.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.