← Home

sails-generate-backend

npm Repository Homepage

Default generator for backend code files in new Sails projects. Creates the default contents of the `api/` and `config/` folders when you run `sails new` on the command line.

24
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

mikermcneilbalderdashysgress454particlebanana

Keywords

backendgeneratorsailsgenerateplugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): The balderdashy→sgress454 transition in 2015 is a well-documented legitimate handoff; sgress454 is a core Sails.js maintainer with a strong track record. Stable for this package. ai

Versions (showing 24 of 24)

Version Deps Published
0.12.8 2 / 3
0.12.6 2 / 3
0.12.5 2 / 3
0.12.4 2 / 3
0.12.3 2 / 3
0.12.2 2 / 3
0.12.0 2 / 3
0.11.3 2 / 3
0.11.2 2 / 3
0.11.1 2 / 3
0.11.0 2 / 3
0.10.13 2 / 3
0.10.12 2 / 3
0.10.11 2 / 3
0.10.10 2 / 3
0.10.9 2 / 3
0.10.8 2 / 3
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.12.8

1 finding
LOW No provenance attestation provenance

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

v0.12.6

1 finding
LOW No provenance attestation provenance

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

v0.12.5

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 → sgress454 (on 2016-02-12) provenance

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

v0.12.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: sgress454 → mikermcneil (on 2016-02-05) provenance

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

v0.12.3

1 finding
LOW No provenance attestation provenance

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

v0.12.2

2 findings
HIGH Publisher changed: balderdashy → sgress454 (on 2015-05-18) provenance

This version was published by a different npm account than previous versions on 2015-05-18. 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.12.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: sgress454 → balderdashy (on 2014-12-19) provenance

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

v0.11.3

1 finding
LOW No provenance attestation provenance

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

v0.11.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-07-30) provenance

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

v0.11.1

1 finding
LOW No provenance attestation provenance

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

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.13

1 finding
LOW No provenance attestation provenance

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

v0.10.12

1 finding
LOW No provenance attestation provenance

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

v0.10.11

1 finding
LOW No provenance attestation provenance

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

v0.10.10

1 finding
LOW No provenance attestation provenance

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

v0.10.9

1 finding
LOW No provenance attestation provenance

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

v0.10.8

1 finding
LOW No provenance attestation provenance

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

v0.10.7

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 2014-03-20) provenance

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

v0.10.6

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 → balderdashy (on 2014-03-05) provenance

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

v0.10.5

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-05) provenance

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

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

1 finding
LOW No provenance attestation provenance

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

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.