karma-requirejs
A Karma plugin. Adapter for RequireJS framework.
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 |
|---|---|---|---|---|
| semgrep | semgrep:eval-usage | AI (semgrep): eval() in lib/require.js is part of the bundled RequireJS library's req.exec() module loader — a well-known, intentional pattern in RequireJS. Not a supply-chain risk for this package. | ai | |
| provenance | no-provenance | AI (provenance): Package is 4783 days old; lack of Sigstore provenance is expected for packages predating the feature. Publisher is well-established and trusted. | ai | |
| provenance | publisher-changed | AI (provenance): dignifiedquire is a listed contributor and has a strong track record; this 2016 transition to the karma-runner org is a documented legitimate handoff, not a compromise. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.1.0 | 0 / 17 | |
| 1.0.0 | 0 / 17 | |
| 0.2.6 | 0 / 17 | |
| 0.2.5 | 0 / 9 | |
| 0.2.4 | 0 / 9 | |
| 0.2.3 | 3 / 6 | |
| 0.2.2 | 0 / 6 | |
| 0.2.1 | 0 / 6 | |
| 0.2.0 | 0 / 6 | |
| 0.1.0 | 0 / 6 | |
| 0.0.3 | 0 / 6 | |
| 0.0.2 | 0 / 6 | |
| 0.0.1 | 0 / 5 |
v1.1.0
2 findingsThis version was published by a different npm account than previous versions on 2016-09-15. 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.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 2016-05-03. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
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 2016-01-28. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.3
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 2016-01-08. This could indicate a legitimate maintainer transition or an account compromise.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.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.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.