mrm-core
Utilities to make tasks for Mrm
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:child-process-import | AI (semgrep): child_process usage is in a test file (execCommand.spec.js) testing the execCommand utility — expected and not production/install-time code. | ai | |
| phantom-deps | phantom-dep:rc | AI (phantom-deps): rc is declared in package.json dependencies; phantom-dep fires because it's referenced via config rather than direct import — not a security concern. | ai | |
| phantom-deps | phantom-dep:babel-code-frame | AI (phantom-deps): babel-code-frame is declared in package.json dependencies; phantom-dep fires due to indirect usage pattern — not a security concern. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 7.1.22 | 20 / 0 | |
| 7.1.21 | 20 / 0 | |
| 7.1.20 | 20 / 0 | |
| 7.1.19 | 20 / 0 | |
| 7.1.18 | 20 / 0 | |
| 7.1.17 | 20 / 0 | |
| 7.1.16 | 20 / 0 | |
| 7.1.15 | 20 / 0 | |
| 7.1.14 | 20 / 0 | |
| 7.1.13 | 20 / 0 | |
| 7.1.12 | 20 / 0 | |
| 7.1.11 | 20 / 0 | |
| 7.1.10 | 20 / 0 | |
| 7.1.9 | 20 / 0 | |
| 7.1.8 | 20 / 0 | |
| 7.1.7 | 20 / 0 | |
| 7.1.6 | 20 / 0 | |
| 7.1.5 | 20 / 0 | |
| 7.1.4 | 20 / 0 | |
| 7.1.3 | 20 / 0 | |
| 7.1.2 | 20 / 0 | |
| 7.1.1 | 20 / 0 | |
| 7.1.0 | 20 / 0 | |
| 7.0.0 | 20 / 0 | |
| 6.1.7 | 20 / 0 | |
| 6.1.6 | 20 / 0 | |
| 6.1.5 | 20 / 0 | |
| 6.1.4 | 20 / 0 | |
| 6.1.3 | 20 / 0 | |
| 6.1.2 | 20 / 0 | |
| 6.1.1 | 20 / 0 | |
| 6.0.0 | 20 / 0 |
v7.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.