sails-stringfile
translated/localized stringfiles containing messages from Sails core and dependencies
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): rachaelshaw is a known Sails.js core team member; transition from balderdashy org account is a documented legitimate handoff within the same organization. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): mikermcneil and rachaelshaw are both well-known Sails.js core maintainers; this is a legitimate team-level maintainer update. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @sailshq/lodash is the official Sails.js scoped lodash fork, a standard replacement for lodash across the entire Sails ecosystem. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in gettext.js loads locale files from a controlled ./locales/ subdirectory path; standard i18n pattern, not arbitrary code execution. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.3.3 | 2 / 0 | |
| 0.3.2 | 2 / 0 | |
| 0.3.1 | 2 / 0 | |
| 0.2.0 | 2 / 0 | |
| 0.1.0 | 2 / 0 | |
| 0.0.1 | 0 / 0 |
v0.3.3
2 findingsThis version was published by a different npm account than previous versions on 2019-04-30. 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.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.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.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.