← Home

waterline-errors

npm Repository Homepage

Standard adapter errors from Waterline

3
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

balderdashyvanetixparticlebanana

Keywords

waterlinesailserrors

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from balderdashy to vanetix occurred in 2014 and is consistent with legitimate authorship — vanetix is the listed author in package.json and the repo URL matches. ai
maintainer-change maintainer-added AI (maintainer-change): vanetix and particlebanana are known Sails.js/Waterline contributors; this 2014 maintainer addition reflects a legitimate project handoff, not a compromise. ai
provenance no-provenance AI (provenance): Package predates Sigstore provenance by many years; absence of attestation is expected for this 2014-era package. ai

Versions (showing 3 of 3)

Version Deps Published
0.10.1 0 / 1
0.9.1 0 / 1
0.9.0 0 / 1

v0.10.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.1

2 findings
HIGH Publisher changed: balderdashy → vanetix (on 2014-02-02) provenance

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

v0.9.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.