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 68 of 168)
| Version | Deps | Published |
|---|---|---|
| 1.10.2 | 9 / 2 | |
| 1.10.1 | 9 / 2 | |
| 1.10.0 | 9 / 2 | |
| 1.9.1 | 9 / 2 | |
| 1.9.0 | 9 / 2 | |
| 1.8.10 | 9 / 2 | |
| 1.8.9 | 9 / 2 | |
| 1.8.8 | 9 / 2 | |
| 1.8.7 | 9 / 2 | |
| 1.8.6 | 9 / 2 | |
| 1.8.5 | 9 / 2 | |
| 1.8.4 | 9 / 2 | |
| 1.8.3 | 9 / 2 | |
| 1.8.2 | 8 / 2 | |
| 1.8.1 | 8 / 2 | |
| 1.8.0 | 8 / 2 | |
| 1.7.1 | 8 / 2 | |
| 1.7.0 | 8 / 2 | |
| 1.6.6 | 8 / 2 | |
| 1.6.5 | 8 / 2 | |
| 1.6.4 | 8 / 2 | |
| 1.6.3 | 8 / 2 | |
| 1.6.2 | 8 / 2 | |
| 1.6.1 | 8 / 2 | |
| 1.6.0 | 8 / 2 | |
| 1.5.1 | 8 / 2 | |
| 1.5.0 | 8 / 2 | |
| 1.4.0 | 7 / 2 | |
| 1.3.0 | 7 / 2 | |
| 1.2.1 | 7 / 2 | |
| 1.2.0 | 7 / 2 | |
| 1.1.4 | 7 / 2 | |
| 1.1.3 | 7 / 2 | |
| 1.1.2 | 7 / 2 | |
| 1.1.1 | 7 / 2 | |
| 1.1.0 | 7 / 2 | |
| 1.0.1 | 19 / 3 | |
| 0.13.0 | 17 / 3 | |
| 0.12.4 | 17 / 3 | |
| 0.12.3 | 17 / 3 | |
| 0.12.2 | 17 / 3 | |
| 0.12.1 | 17 / 3 | |
| 0.12.0 | 16 / 3 | |
| 0.11.6 | 16 / 3 | |
| 0.11.5 | 15 / 3 | |
| 0.11.2 | 15 / 3 | |
| 0.11.1 | 15 / 3 | |
| 0.11.0 | 15 / 3 | |
| 0.10.3 | 15 / 3 | |
| 0.10.2 | 14 / 3 | |
| 0.10.1 | 15 / 3 | |
| 0.10.0 | 15 / 3 | |
| 0.1.1 | 15 / 3 | |
| 0.0.16 | 15 / 3 | |
| 0.0.15 | 15 / 3 | |
| 0.0.14 | 15 / 3 | |
| 0.0.13 | 15 / 3 | |
| 0.0.12 | 13 / 0 | |
| 0.0.11 | 16 / 2 | |
| 0.0.10 | 16 / 2 | |
| 0.0.8 | 8 / 2 | |
| 0.0.7 | 7 / 3 | |
| 0.0.6 | 7 / 3 | |
| 0.0.5 | 7 / 3 | |
| 0.0.4 | 7 / 3 | |
| 0.0.3 | 7 / 3 | |
| 0.0.2 | 7 / 3 | |
| 0.0.1 | 3 / 1 |
v1.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.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.
v1.8.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.