sails-disk
Persistent local-disk (and/or memory) adapter for Sails.js / Waterline.
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): mikermcneil is the founder of The Sails Company and canonical owner of the sails-disk package; publisher transitions within this org are expected and legitimate. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): rachaelshaw is a known Sails.js core team member; adding her as maintainer is routine team management within The Sails Company. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): flaverr is a Sails.js ecosystem utility from the same organization; its addition is a legitimate dependency, not a supply-chain injection. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 2.1.2 | 5 / 3 | |
| 2.1.1 | 5 / 3 | |
| 2.1.0 | 5 / 3 | |
| 2.0.0 | 5 / 3 | |
| 1.1.2 | 4 / 3 | |
| 1.1.1 | 4 / 3 | |
| 1.1.0 | 4 / 3 | |
| 1.0.1 | 4 / 3 | |
| 1.0.0 | 4 / 3 | |
| 0.10.10 | 6 / 3 | |
| 0.10.9 | 6 / 3 | |
| 0.10.8 | 6 / 3 | |
| 0.10.7 | 6 / 3 | |
| 0.10.6 | 6 / 3 | |
| 0.10.5 | 6 / 3 | |
| 0.10.4 | 6 / 3 | |
| 0.10.3 | 6 / 3 | |
| 0.10.2 | 6 / 3 | |
| 0.10.1 | 5 / 3 | |
| 0.9.3 | 3 / 2 | |
| 0.9.2 | 3 / 2 | |
| 0.9.1 | 3 / 2 | |
| 0.9.0 | 3 / 2 | |
| 0.1.0 | 3 / 2 |
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
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 2021-11-09. This could indicate a legitimate maintainer transition or an account compromise.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
2 findingsThis version was published by a different npm account than previous versions on 2020-05-26. 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.
v1.1.2
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 2019-04-25. This could indicate a legitimate maintainer transition or an account compromise.
v1.1.1
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 2019-04-24. This could indicate a legitimate maintainer transition or an account compromise.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
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 2018-04-04. This could indicate a legitimate maintainer transition or an account compromise.