sails-generate-gruntfile
Generate a gruntfile for Sails.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:grunt-contrib-uglify | AI (phantom-deps): grunt plugin optionalDependency for Gruntfile generator; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:grunt-contrib-clean | AI (phantom-deps): grunt plugin optionalDependency for Gruntfile generator; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:grunt-contrib-watch | AI (phantom-deps): grunt plugin optionalDependency for Gruntfile generator; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:grunt-contrib-coffee | AI (phantom-deps): grunt plugin optionalDependency for Gruntfile generator; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:grunt-contrib-concat | AI (phantom-deps): grunt plugin optionalDependency for Gruntfile generator; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:grunt-contrib-cssmin | AI (phantom-deps): grunt plugin optionalDependency for Gruntfile generator; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:grunt | AI (phantom-deps): grunt is an optionalDependency of a Gruntfile generator; it doesn't need to be directly imported in the generator's JS code. | ai | |
| phantom-deps | phantom-dep:grunt-cli | AI (phantom-deps): grunt-cli is an optionalDependency of a Gruntfile generator; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:grunt-contrib-jst | AI (phantom-deps): grunt plugin optionalDependency for Gruntfile generator; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:grunt-contrib-copy | AI (phantom-deps): grunt plugin optionalDependency for Gruntfile generator; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:grunt-contrib-less | AI (phantom-deps): grunt plugin optionalDependency for Gruntfile generator; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:grunt-sails-linker | AI (phantom-deps): grunt plugin optionalDependency for Gruntfile generator; not directly imported by design. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): 0.0.0 is a legitimate initial release pattern in the Sails.js generator ecosystem from the established balderdashy publisher; not a malware indicator. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scaffold/generator package intentionally has no runtime deps and minimal entry point; this is expected for a Sails generator that bundles a Gruntfile template. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): mikermcneil is the founder of Sails.js/Balderdashy; adding him as maintainer is expected organizational housekeeping for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Package is a stable Sails ~0.10.0 gruntfile generator; long dormancy between maintenance releases is normal for this type of utility. | ai | |
| provenance | publisher-changed | AI (provenance): sgress454 is a known Sails.js core contributor (1376 approved packages); the balderdashy→sgress454 transition is a legitimate org handoff, not a compromise. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.10.11 | 2 / 3 | |
| 0.10.10 | 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 | 14 / 3 | |
| 0.10.2 | 2 / 3 | |
| 0.10.1 | 0 / 0 | |
| 0.10.0 | 0 / 0 | |
| 0.1.0 | 0 / 0 | |
| 0.0.0 | 0 / 0 |
v0.10.11
2 findingsThis version was published by a different npm account than previous versions on 2016-07-08. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.8
2 findingsPackage 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 2014-03-01. This could indicate a legitimate maintainer transition or an account compromise.
v0.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
2 findingsPackage 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 2014-01-31. This could indicate a legitimate maintainer transition or an account compromise.
v0.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.