sails-generate-api — Greenflagged

Generate a Sails API.

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

sgress454

Keywords

controllermodelapigeneratorsailsgenerateplugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:async	AI (phantom-deps): async is declared in dependencies and used by the generator; phantom classification is a false positive for this package.	ai	2026/04/24
phantom-deps	phantom-dep:lodash	AI (phantom-deps): lodash is declared in dependencies and used by the generator; phantom classification is a false positive for this package.	ai	2026/04/24
phantom-deps	phantom-dep:merge-defaults	AI (phantom-deps): merge-defaults is declared in dependencies and used by the generator; phantom classification is a false positive for this package.	ai	2026/04/24

Versions (showing 2 of 2)

Version	Deps	Published
0.10.1	3 / 5	2016-07-08
0.10.0	3 / 5	2014-08-29

v0.10.1

1 finding

LOW No provenance attestation provenance

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

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.