@ordergroove/smi-serve
Utility to serve a Subscription Manager template locally
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): JWT payload decoding — standard auth pattern, not obfuscation. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): 0.0.0.0:3000 is a local dev environment fallback URL, not exfiltration. | ai | |
| semgrep | semgrep:toplevel-fetch | AI (semgrep): Fetches a config JSON for cancel-flow; expected behavior for a local dev server tool. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): CLI dev-server tool legitimately uses child_process to spawn subprocesses. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 1.14.0 | 9 / 1 | |
| 1.13.4 | 9 / 1 | |
| 1.13.3 | 9 / 1 | |
| 1.13.2 | 9 / 1 | |
| 1.13.1 | 9 / 1 | |
| 1.12.1 | 9 / 1 | |
| 1.12.0 | 9 / 1 | |
| 1.11.0 | 9 / 1 | |
| 1.10.1 | 9 / 1 | |
| 1.10.0 | 9 / 1 | |
| 1.9.24 | 9 / 1 | |
| 1.9.23 | 9 / 1 | |
| 1.9.22 | 9 / 1 | |
| 1.9.21 | 9 / 1 | |
| 1.9.20 | 10 / 1 | |
| 1.9.19 | 10 / 1 | |
| 1.9.18 | 10 / 1 | |
| 1.9.17 | 10 / 1 | |
| 1.9.16 | 10 / 1 |
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.