karma-coffee-preprocessor MIT 13 versions

karma-coffee-preprocessor

npm Repository Homepage

A Karma plugin. Compile coffee script on the fly.

13

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

vojtajinazzodignifiedquire

Keywords

karma-pluginkarma-preprocessorcoffee-scriptcoffee

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher change (zzo → dignifiedquire) occurred in 2016; dignifiedquire is listed as a contributor and has a strong track record (578/0). Legitimate maintainer transition under karma-runner org.	ai	2026/04/23
publish-pattern	new-deps-added	AI (publish-pattern): object-assign is a well-known, widely-trusted utility package. Its addition is benign and consistent with standard JS development practices.	ai	2026/04/23

Versions (showing 13 of 13)

Version	Deps	Published
1.0.1	2 / 10	2016-07-12
1.0.0	1 / 8	2016-05-04
0.3.0	1 / 8	2015-07-09
0.2.1	1 / 4	2014-03-13
0.2.0	1 / 4	2014-03-11
0.1.3	1 / 4	2014-02-14
0.1.2	1 / 4	2013-12-26
0.1.1	1 / 4	2013-11-26
0.1.0	1 / 4	2013-08-06
0.0.4	1 / 4	2013-08-05
0.0.3	1 / 4	2013-07-19
0.0.2	1 / 4	2013-07-05
0.0.1	1 / 0	2013-03-20

v1.0.1

2 findings

HIGH Publisher changed: zzo → dignifiedquire (on 2016-07-12) provenance

This version was published by a different npm account than previous versions on 2016-07-12. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.0.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: dignifiedquire → zzo (on 2016-05-04) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2016-05-04. This could indicate a legitimate maintainer transition or an account compromise.

v0.3.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: vojtajina → dignifiedquire (on 2015-07-09) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2015-07-09. This could indicate a legitimate maintainer transition or an account compromise.

v0.2.1

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.3

1 finding

LOW No provenance attestation provenance

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

v0.1.2

1 finding

LOW No provenance attestation provenance

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

v0.1.1

1 finding

LOW No provenance attestation provenance

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

v0.1.0

1 finding

LOW No provenance attestation provenance

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

v0.0.4

1 finding

LOW No provenance attestation provenance

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

v0.0.3

1 finding

LOW No provenance attestation provenance

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

v0.0.2

1 finding

LOW No provenance attestation provenance

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

v0.0.1

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.