@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, so a manually published version cannot be tied back to a reviewed commit.
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 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 1.15.3 | 9 / 3 | |
| 1.15.2 | 9 / 3 | |
| 1.15.1 | 9 / 3 | |
| 1.15.0 | 9 / 3 | |
| 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 | |
| 1.9.15 | 10 / 1 | |
| 1.9.14 | 10 / 1 | |
| 1.9.13 | 10 / 1 | |
| 1.9.11 | 10 / 1 | |
| 1.9.10 | 10 / 1 | |
| 1.9.9 | 10 / 1 | |
| 1.9.8 | 10 / 1 | |
| 1.9.7 | 10 / 1 | |
| 1.9.6 | 10 / 1 | |
| 1.9.5 | 10 / 1 | |
| 1.9.4 | 10 / 1 | |
| 1.9.3 | 10 / 1 | |
| 1.9.2 | 10 / 1 | |
| 1.9.1 | 10 / 1 | |
| 1.9.0 | 10 / 1 | |
| 1.8.9 | 10 / 1 | |
| 1.8.8 | 10 / 1 | |
| 1.8.7 | 10 / 1 | |
| 1.8.6 | 10 / 1 | |
| 1.8.5 | 10 / 1 | |
| 1.8.4 | 10 / 1 | |
| 1.8.3 | 10 / 1 |
v1.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.13
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (brian-lewis-5) than the most recent previously approved version (ogdevs) on 2025-02-03, but brian-lewis-5 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.9.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.