@steedos/meteor-bundle-runner
Run meteor bundles and inject your own nodejs code.
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-execsync | AI (semgrep): Hardcoded 'npm root -g' command to locate global npm path; not user-controlled input. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used only for 'npm root -g'; consistent with bundle runner functionality. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is core to Meteor bundle runner loading server programs; stable pattern across versions. | ai | |
| phantom-deps | phantom-dep:promise | AI (phantom-deps): Phantom dep heuristic false positive for this package's dependency structure. | ai | |
| phantom-deps | phantom-dep:meteor-promise | AI (phantom-deps): Phantom dep heuristic false positive for this package's dependency structure. | ai | |
| phantom-deps | phantom-dep:@mapbox/node-pre-gyp | AI (phantom-deps): Phantom dep heuristic false positive; used transitively by native deps. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 2.7.32 | 8 / 0 | |
| 2.7.31 | 8 / 0 | |
| 2.7.30 | 8 / 0 | |
| 2.7.29 | 8 / 0 | |
| 2.7.28 | 8 / 0 | |
| 2.7.27 | 8 / 0 | |
| 2.7.25 | 8 / 0 | |
| 2.7.24 | 8 / 0 | |
| 2.7.22 | 8 / 0 | |
| 2.7.21 | 8 / 0 | |
| 2.7.20 | 8 / 0 | |
| 2.7.19 | 8 / 0 | |
| 2.7.18 | 8 / 0 |
v2.7.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.