sass-loader
Sass loader for webpack
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:pify | AI (dependencies): pify is a widely-used, well-known promisification utility; its use in sass-loader for async webpack loading is expected and benign across all versions. | ai | |
| provenance | publisher-changed | AI (provenance): evilebottnawi (Alexander Akutov) is the established webpack ecosystem maintainer; publisher change from jhnns happened years ago and is legitimate. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Added maintainers (sokra, evilebottnawi, ev1stensberg) are core webpack team members; legitimate team evolution. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers reflect natural project evolution over many years under the webpack org. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy is an artifact of diff baseline (v7.1.0); sass-loader has been continuously published on npm. | ai | |
| provenance | no-provenance | AI (provenance): sass-loader is a well-established webpack-contrib package predating Sigstore provenance; absence is expected and not a risk signal for this package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 16.0.7 | 1 / 48 | |
| 16.0.6 | 1 / 48 | |
| 16.0.5 | 1 / 39 | |
| 16.0.4 | 1 / 39 | |
| 16.0.3 | 1 / 39 | |
| 16.0.2 | 1 / 39 | |
| 16.0.1 | 1 / 39 | |
| 16.0.0 | 1 / 39 | |
| 15.0.0 | 1 / 39 | |
| 8.0.2 | 5 / 35 | |
| 7.1.0 | 6 / 18 |
v16.0.7
2 findings[Accepted risk] Package 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 2026-02-05. This could indicate a legitimate maintainer transition or an account compromise.
v16.0.6
2 findings[Accepted risk] Package 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 2025-10-23. This could indicate a legitimate maintainer transition or an account compromise.
v16.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.0
2 findings[Accepted risk] Package 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 2024-07-26. This could indicate a legitimate maintainer transition or an account compromise.
v15.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.2
2 findings[Accepted risk] Package 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 2020-01-13. This could indicate a legitimate maintainer transition or an account compromise.