sails-generate-new MIT 28 versions

sails-generate-new

npm

Generate a new Sails app.

28

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

balderdashymikermcneilsgress454

Keywords

controllergeneratorsailsgenerateplugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher change balderdashy→sgress454 occurred in Jan 2014; sgress454 is a known Sails.js core contributor with 1401 approved packages. Clearly a legitimate historical transition.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): sgress454 added as maintainer in 2014 as part of legitimate Sails.js core team transition; not a recent or suspicious change.	ai	2026/04/24
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require loads scope.rootPath+'/package.json' — reads a JSON file at a known path during scaffolding. Not arbitrary module loading; standard generator behavior.	ai	2026/04/24

Versions (showing 28 of 28)

Version	Deps	Published
0.10.29	5 / 5	2016-10-05
0.10.28	5 / 5	2016-07-08
0.10.27	5 / 5	2016-03-31
0.10.26	5 / 5	2016-02-05
0.10.25	5 / 5	2016-01-24
0.10.24	5 / 5	2016-01-13
0.10.23	5 / 5	2016-01-05
0.10.22	5 / 5	2015-10-10
0.10.21	3 / 6	2015-06-18
0.10.20	3 / 6	2015-06-11
0.10.19	3 / 6	2015-05-18
0.10.18	3 / 6	2014-09-01
0.10.17	3 / 6	2014-07-26
0.10.16	3 / 6	2014-06-26
0.10.15	3 / 6	2014-04-04
0.10.14	3 / 6	2014-03-05
0.10.13	3 / 6	2014-03-05
0.10.12	3 / 6	2014-03-05
0.10.11	3 / 6	2014-03-01
0.10.10	3 / 6	2014-02-13
0.10.9	3 / 6	2014-01-31
0.10.7	3 / 6	2014-01-22
0.10.6	3 / 6	2014-01-21
0.10.4	3 / 6	2014-01-20
0.10.3	6 / 3	2014-01-20
0.10.2	5 / 3	2014-01-17
0.10.1	1 / 0	2014-01-12
0.10.0	0 / 0	2014-01-12

v0.10.29

1 finding

LOW No provenance attestation provenance

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

v0.10.28

1 finding

LOW No provenance attestation provenance

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

v0.10.27

2 findings

HIGH Publisher changed: mikermcneil → sgress454 (on 2016-03-31) provenance

This version was published by a different npm account than previous versions on 2016-03-31. 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.26

2 findings

HIGH Publisher changed: sgress454 → mikermcneil (on 2016-02-05) provenance

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.

LOW No provenance attestation provenance

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

v0.10.25

1 finding

LOW No provenance attestation provenance

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

v0.10.24

1 finding

LOW No provenance attestation provenance

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

v0.10.23

1 finding

LOW No provenance attestation provenance

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

v0.10.22

1 finding

LOW No provenance attestation provenance

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

v0.10.21

1 finding

LOW No provenance attestation provenance

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

v0.10.20

1 finding

LOW No provenance attestation provenance

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

v0.10.19

1 finding

LOW No provenance attestation provenance

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

v0.10.18

2 findings

HIGH Publisher changed: balderdashy → sgress454 (on 2014-09-01) provenance

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

2 findings

HIGH Publisher changed: balderdashy → sgress454 (on 2014-07-26) provenance

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

2 findings

HIGH Publisher changed: balderdashy → sgress454 (on 2014-06-26) provenance

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

2 findings

HIGH Publisher changed: balderdashy → sgress454 (on 2014-04-04) provenance

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

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

2 findings

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

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

2 findings

HIGH Publisher changed: balderdashy → sgress454 (on 2014-02-13) provenance

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

2 findings

HIGH Publisher changed: balderdashy → sgress454 (on 2014-01-31) provenance

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

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.

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