@financial-times/dotcom-build-sass MIT 21 versions

@financial-times/dotcom-build-sass

npm Homepage

This package exports a Webpack plugin to configure it with a way to load and generate CSS files from [Sass] source code.

21

Versions

MIT

License

No

Install Scripts

Missing

Provenance

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

the-ftrowanmanningcheealexwilsonaendraemmalewisnotleeseraph2000hamza.samihrobertboultonrobgodfrey

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:dynamic-require	AI (semgrep): Resolves user-configured sass implementation name (e.g. 'sass-embedded'); standard sass-loader pattern, not arbitrary module loading.	ai	2026/04/29
phantom-deps	phantom-dep:sass-embedded	AI (phantom-deps): sass-embedded is a declared runtime dependency; used via dynamic require for sass implementation selection.	ai	2026/04/29

Versions (showing 21 of 21)

Version	Deps	Published
13.10.0	3 / 0	2026-04-27
13.9.2	3 / 0	2026-03-26
13.9.1	3 / 0	2026-03-25
13.9.0	3 / 0	2026-03-18
13.8.1	3 / 0	2026-03-10
13.8.0	3 / 0	2026-03-05
13.7.1	3 / 0	2026-02-20
13.7.0	3 / 0	2026-01-05
13.6.1	3 / 0	2025-12-17
13.6.0	3 / 0	2025-12-15
13.5.1	3 / 0	2025-12-12
13.5.0	3 / 0	2025-12-09
13.4.0	3 / 0	2025-10-31
13.3.0	3 / 0	2025-10-01
13.2.3	3 / 0	2025-09-18
13.2.2	3 / 0	2025-09-04
13.2.1	3 / 0	2025-09-03
13.2.0	3 / 0	2025-09-02
13.1.0	3 / 0	2025-08-22
13.0.1	3 / 0	2025-07-03
13.0.0	3 / 0	2025-07-02

v13.9.2

1 finding

LOW No provenance attestation provenance

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

v13.9.1

1 finding

LOW No provenance attestation provenance

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

v13.9.0

1 finding

LOW No provenance attestation provenance

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

v13.8.1

1 finding

LOW No provenance attestation provenance

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

v13.8.0

1 finding

LOW No provenance attestation provenance

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

v13.7.1

1 finding

LOW No provenance attestation provenance

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

v13.7.0

1 finding

LOW No provenance attestation provenance

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

v13.6.1

1 finding

LOW No provenance attestation provenance

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

v13.6.0

1 finding

LOW No provenance attestation provenance

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

v13.5.1

1 finding

LOW No provenance attestation provenance

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

v13.5.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.

v13.4.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.

v13.3.0

1 finding

LOW No provenance attestation provenance

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

v13.2.3

1 finding

LOW No provenance attestation provenance

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

v13.2.2

1 finding

LOW No provenance attestation provenance

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

v13.2.1

1 finding

LOW No provenance attestation provenance

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

v13.2.0

1 finding

LOW No provenance attestation provenance

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

v13.1.0

1 finding

LOW No provenance attestation provenance

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

v13.0.1

1 finding

LOW No provenance attestation provenance

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

v13.0.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.