← Home

sails-generate-adapter

npm

Generate a adapter for Sails.

7
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

sgress454balderdashy

Keywords

adaptergeneratorsailsgenerateplugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): The 2014 transfer from sgress454 to balderdashy is a decade-old legitimate org consolidation by the official Sails.js maintainers; not a compromise signal. ai

Versions (showing 7 of 7)

Version Deps Published
0.10.7 2 / 3
0.10.6 2 / 3
0.10.5 2 / 3
0.10.4 2 / 3
0.10.3 2 / 3
0.10.2 2 / 3
0.10.1 2 / 3

v0.10.7

1 finding
LOW No provenance attestation provenance

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

v0.10.6

1 finding
LOW No provenance attestation provenance

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

v0.10.5

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

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 → sgress454 (on 2014-03-07) provenance

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

v0.10.3

2 findings
HIGH Publisher changed: sgress454 → balderdashy (on 2014-03-03) provenance

This version was published by a different npm account than previous versions on 2014-03-03. 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.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: balderdashy → sgress454 (on 2014-02-14) provenance

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

v0.10.1

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.