sails-hook-orm MIT 23 versions

sails-hook-orm

npm Repository Homepage

The ORM hook from Sails core.

23

Versions

MIT

License

No

Install Scripts

Missing

Provenance

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

particlebananarachaelshawsgress454mikermcneileashaw

Keywords

waterlineormsailshooksails-hook

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): eashaw is a long-standing Balderdashy org member (852 approved packages, 2059 days history); this is a legitimate maintainer transition within the SailsJS org, not a takeover.	ai	2026/04/24
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require of adapter paths is the core design pattern for this ORM hook — it loads user-configured database adapters. Intentional and expected behavior for this package.	ai	2026/04/24

Versions (showing 23 of 23)

Version	Deps	Published
4.0.3	9 / 3	2024-03-15
4.0.2	9 / 3	2022-08-10
4.0.1	9 / 3	2022-01-10
4.0.0	9 / 3	2021-10-22
3.0.2	9 / 3	2021-03-10
3.0.1	9 / 3	2020-05-26
3.0.0	9 / 3	2020-05-26
2.1.1	9 / 3	2018-10-17
2.1.0	9 / 3	2018-07-24
2.0.1	9 / 3	2018-05-06
2.0.0	9 / 3	2018-03-28
1.0.9	5 / 2	2016-11-06
1.0.8	6 / 2	2016-11-05
1.0.7	5 / 2	2016-10-06
1.0.6	5 / 2	2016-04-02
1.0.5	5 / 2	2016-04-01
1.0.4	5 / 2	2016-04-01
1.0.3	5 / 0	2016-03-15
1.0.2	5 / 0	2016-03-14
1.0.1	5 / 0	2016-03-13
1.0.0	5 / 0	2016-03-07
0.2.0	5 / 0	2016-01-22
0.1.0	5 / 0	2016-01-19

v4.0.3

1 finding

LOW No provenance attestation provenance

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

v4.0.2

2 findings

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

This version was published by a different npm account than previous versions on 2022-08-10. 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.

v4.0.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: eashaw → mikermcneil (on 2022-01-10) provenance

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

v4.0.0

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: mikermcneil → eashaw (on 2021-10-22) provenance

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

v3.0.2

1 finding

LOW No provenance attestation provenance

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

v3.0.1

1 finding

LOW No provenance attestation provenance

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

v3.0.0

1 finding

LOW No provenance attestation provenance

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