sails-generate
Runner script for sails generators
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): sails-generate is a scaffolding tool that legitimately spawns child processes (e.g., npm install) as part of its generator workflow. This is expected and documented behavior. | ai | |
| phantom-deps | phantom-dep:sails-generate-helper | AI (phantom-deps): Plugin dynamically loaded by name; phantom-dep is expected for plugin-based architecture. | ai | |
| phantom-deps | phantom-dep:sails-generate-generator | AI (phantom-deps): Plugin dynamically loaded by name; phantom-dep is expected for plugin-based architecture. | ai | |
| phantom-deps | phantom-dep:sails-generate-gruntfile | AI (phantom-deps): Plugin dynamically loaded by name; phantom-dep is expected for plugin-based architecture. | ai | |
| phantom-deps | phantom-dep:sails-generate-controller | AI (phantom-deps): Plugin dynamically loaded by name; phantom-dep is expected for plugin-based architecture. | ai | |
| phantom-deps | phantom-dep:sails-generate-views-jade | AI (phantom-deps): Plugin dynamically loaded by name; phantom-dep is expected for plugin-based architecture. | ai | |
| phantom-deps | phantom-dep:sails-generate-sails.io.js | AI (phantom-deps): Plugin dynamically loaded by name; phantom-dep is expected for plugin-based architecture. | ai | |
| phantom-deps | phantom-dep:sails-generate-api | AI (phantom-deps): Plugin dynamically loaded by name; phantom-dep is expected for plugin-based architecture. | ai | |
| phantom-deps | phantom-dep:sails-generate-new | AI (phantom-deps): Plugin dynamically loaded by name; phantom-dep is expected for plugin-based architecture. | ai | |
| phantom-deps | phantom-dep:sails-generate-model | AI (phantom-deps): Plugin dynamically loaded by name; phantom-dep is expected for plugin-based architecture. | ai | |
| phantom-deps | phantom-dep:sails-generate-views | AI (phantom-deps): Plugin dynamically loaded by name; phantom-dep is expected for plugin-based architecture. | ai | |
| phantom-deps | phantom-dep:sails-generate-action | AI (phantom-deps): Plugin dynamically loaded by name; phantom-dep is expected for plugin-based architecture. | ai | |
| phantom-deps | phantom-dep:sails-generate-adapter | AI (phantom-deps): Plugin dynamically loaded by name; phantom-dep is expected for plugin-based architecture. | ai | |
| phantom-deps | phantom-dep:sails-generate-backend | AI (phantom-deps): Plugin dynamically loaded by name; phantom-dep is expected for plugin-based architecture. | ai | |
| phantom-deps | phantom-dep:sails-generate-frontend | AI (phantom-deps): Plugin dynamically loaded by name; phantom-dep is expected for plugin-based architecture. | ai | |
| provenance | publisher-changed | AI (provenance): eashaw is a known Sails.js team member (853 approved packages, 2059 days history). Publisher change from rachaelshaw to eashaw is a legitimate org-internal transition. | ai | |
| phantom-deps | phantom-dep:cross-spawn | AI (phantom-deps): cross-spawn is explicitly declared in dependencies; static analysis may not detect all import paths. Benign false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established Balderdashy package with 4485-day history; lack of Sigstore provenance is not a material risk signal here. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() appears in a bundled Vue.js scaffold template file — Vue's internal template compiler; legitimate and stable for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require() is used to validate package.json paths in generator tooling — standard pattern for sails-generate, not arbitrary code execution. | ai |
Versions (showing 51 of 168)
| Version | Deps | Published |
|---|---|---|
| 2.0.13 | 10 / 3 | |
| 2.0.12 | 11 / 3 | |
| 2.0.11 | 11 / 3 | |
| 2.0.10 | 11 / 3 | |
| 2.0.9 | 11 / 3 | |
| 2.0.8 | 11 / 3 | |
| 2.0.7 | 11 / 3 | |
| 2.0.6 | 11 / 3 | |
| 2.0.5 | 11 / 3 | |
| 2.0.4 | 11 / 3 | |
| 2.0.3 | 11 / 3 | |
| 2.0.2 | 11 / 3 | |
| 2.0.1 | 11 / 3 | |
| 2.0.0 | 11 / 3 | |
| 1.17.2 | 11 / 3 | |
| 1.17.1 | 11 / 3 | |
| 1.17.0 | 11 / 3 | |
| 1.16.13 | 11 / 3 | |
| 1.16.12 | 11 / 3 | |
| 1.16.11 | 11 / 3 | |
| 1.16.10 | 11 / 3 | |
| 1.16.9 | 11 / 3 | |
| 1.16.8 | 11 / 3 | |
| 1.16.7 | 11 / 3 | |
| 1.16.6 | 11 / 3 | |
| 1.16.5 | 11 / 3 | |
| 1.16.4 | 11 / 3 | |
| 1.16.3 | 11 / 3 | |
| 1.16.2 | 11 / 3 | |
| 1.16.1 | 11 / 3 | |
| 1.16.0 | 11 / 3 | |
| 1.15.28 | 11 / 3 | |
| 1.15.27 | 11 / 3 | |
| 1.15.26 | 11 / 3 | |
| 1.15.25 | 11 / 3 | |
| 1.15.24 | 11 / 3 | |
| 1.15.23 | 11 / 3 | |
| 1.15.22 | 11 / 3 | |
| 1.15.21 | 11 / 3 | |
| 1.15.20 | 11 / 3 | |
| 1.15.19 | 11 / 3 | |
| 1.15.18 | 11 / 3 | |
| 1.15.17 | 11 / 3 | |
| 1.15.16 | 11 / 3 | |
| 1.15.15 | 11 / 3 | |
| 1.15.14 | 11 / 3 | |
| 1.15.13 | 11 / 3 | |
| 1.15.12 | 11 / 3 | |
| 1.15.11 | 11 / 3 | |
| 1.15.10 | 11 / 3 | |
| 1.15.9 | 11 / 3 |
v2.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-03-10. This could indicate a legitimate maintainer transition or an account compromise.
v2.0.2
2 findingsThis version was published by a different npm account than previous versions on 2021-02-22. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-05-14. This could indicate a legitimate maintainer transition or an account compromise.
v1.17.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-05-08. This could indicate a legitimate maintainer transition or an account compromise.
v1.17.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-05-07. This could indicate a legitimate maintainer transition or an account compromise.
v1.16.13
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-06-12. This could indicate a legitimate maintainer transition or an account compromise.
v1.16.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.8
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-04-22. This could indicate a legitimate maintainer transition or an account compromise.
v1.16.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.17
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-03-31. This could indicate a legitimate maintainer transition or an account compromise.
v1.15.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.15
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-03-28. This could indicate a legitimate maintainer transition or an account compromise.
v1.15.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.