@nimee/api-clients
communication http for each ms
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@nimee/logger | AI (phantom-deps): Same-org scoped dependency, likely used indirectly; stable false positive. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IPs are localhost dev fallbacks via env var; internal service mesh URLs are not malicious. Stable pattern across this package. | ai |
Versions (showing 94 of 94)
| Version | Deps | Published |
|---|---|---|
| 1.1.96 | 4 / 14 | |
| 1.1.95 | 4 / 14 | |
| 1.1.94 | 4 / 14 | |
| 1.1.93 | 4 / 14 | |
| 1.1.89 | 4 / 14 | |
| 1.1.88 | 4 / 14 | |
| 1.1.87 | 4 / 14 | |
| 1.1.81 | 4 / 14 | |
| 1.1.80 | 4 / 14 | |
| 1.1.79 | 4 / 14 | |
| 1.1.78 | 4 / 14 | |
| 1.1.77 | 4 / 14 | |
| 1.1.76 | 4 / 14 | |
| 1.1.75 | 4 / 14 | |
| 1.1.74 | 4 / 14 | |
| 1.1.73 | 4 / 14 | |
| 1.1.72 | 4 / 14 | |
| 1.1.71 | 4 / 14 | |
| 1.1.70 | 4 / 14 | |
| 1.1.69 | 4 / 14 | |
| 1.1.68 | 4 / 14 | |
| 1.1.67 | 4 / 14 | |
| 1.1.66 | 4 / 14 | |
| 1.1.65 | 4 / 14 | |
| 1.1.64 | 4 / 14 | |
| 1.1.63 | 4 / 14 | |
| 1.1.62 | 4 / 14 | |
| 1.1.61 | 4 / 14 | |
| 1.1.60 | 4 / 14 | |
| 1.1.59 | 4 / 14 | |
| 1.1.58 | 4 / 14 | |
| 1.1.57 | 4 / 14 | |
| 1.1.55 | 4 / 14 | |
| 1.1.54 | 4 / 14 | |
| 1.1.53 | 4 / 14 | |
| 1.1.52 | 4 / 14 | |
| 1.1.51 | 4 / 14 | |
| 1.1.50 | 4 / 14 | |
| 1.1.49 | 4 / 14 | |
| 1.1.48 | 4 / 14 | |
| 1.1.47 | 4 / 14 | |
| 1.1.46 | 4 / 14 | |
| 1.1.45 | 4 / 14 | |
| 1.1.44 | 4 / 14 | |
| 1.1.43 | 4 / 14 | |
| 1.1.42 | 4 / 14 | |
| 1.1.41 | 4 / 14 | |
| 1.1.40 | 4 / 14 | |
| 1.1.39 | 4 / 14 | |
| 1.1.37 | 4 / 14 | |
| 1.1.35 | 4 / 14 | |
| 1.1.34 | 4 / 14 | |
| 1.1.33 | 4 / 14 | |
| 1.1.32 | 4 / 14 | |
| 1.1.31 | 4 / 14 | |
| 1.1.30 | 4 / 14 | |
| 1.1.29 | 4 / 14 | |
| 1.1.28 | 4 / 14 | |
| 1.1.27 | 4 / 14 | |
| 1.1.26 | 4 / 14 | |
| 1.1.25 | 4 / 14 | |
| 1.1.24 | 4 / 14 | |
| 1.1.23 | 4 / 14 | |
| 1.1.22 | 4 / 14 | |
| 1.1.21 | 4 / 14 | |
| 1.1.20 | 4 / 14 | |
| 1.1.19 | 4 / 14 | |
| 1.1.18 | 4 / 14 | |
| 1.1.17 | 4 / 14 | |
| 1.1.16 | 4 / 14 | |
| 1.1.15 | 4 / 14 | |
| 1.1.14 | 4 / 14 | |
| 1.1.13 | 4 / 14 | |
| 1.1.12 | 4 / 14 | |
| 1.1.11 | 3 / 14 | |
| 1.1.10 | 3 / 14 | |
| 1.1.9 | 3 / 14 | |
| 1.1.8 | 3 / 14 | |
| 1.1.7 | 3 / 14 | |
| 1.1.6 | 3 / 14 | |
| 1.1.5 | 3 / 8 | |
| 1.1.4 | 3 / 8 | |
| 1.1.3 | 3 / 8 | |
| 1.1.2 | 3 / 8 | |
| 1.0.9 | 3 / 8 | |
| 1.0.8 | 3 / 8 | |
| 1.0.7 | 3 / 8 | |
| 1.0.6 | 3 / 8 | |
| 1.0.5 | 3 / 8 | |
| 1.0.4 | 3 / 8 | |
| 1.0.3 | 3 / 8 | |
| 1.0.2 | 3 / 8 | |
| 1.0.1 | 3 / 8 | |
| 1.0.0 | 2 / 8 |
v1.1.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.95
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 (sarkis122) than the most recent previously approved version (kalitas) on 2026-07-06, but sarkis122 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.1.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.68
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 (kalitas) than the most recent previously approved version (shmuel_nimi) on 2025-03-30, but kalitas 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.1.67
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 (kalitas) than the most recent previously approved version (shmuel_nimi) on 2025-03-27, but kalitas 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.1.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.65
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 (kalitas) than the most recent previously approved version (shmuel_nimi) on 2025-03-16, but kalitas 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.1.64
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 (shmuel_nimi) than the most recent previously approved version (kalitas) on 2025-03-15, but shmuel_nimi 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.1.63
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 (shmuel_nimi) than the most recent previously approved version (kalitas) on 2025-03-12, but shmuel_nimi 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.1.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.61
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 (shmuel_nimi) than the most recent previously approved version (kalitas) on 2025-03-11, but shmuel_nimi 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.1.60
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 (kalitas) than the most recent previously approved version (shmuel_nimi) on 2025-03-04, but kalitas 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.1.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.57
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 (kalitas) than the most recent previously approved version (shmuel_nimi) on 2025-02-19, but kalitas 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.1.55
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 (shmuel_nimi) than the most recent previously approved version (kalitas) on 2025-02-16, but shmuel_nimi 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.1.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.52
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 (kalitas) than the most recent previously approved version (shmuel_nimi) on 2025-01-23, but kalitas 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.1.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.50
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 (shmuel_nimi) than the most recent previously approved version (kalitas) on 2024-12-03, but shmuel_nimi 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.1.49
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 (kalitas) than the most recent previously approved version (shmuel_nimi) on 2024-11-26, but kalitas 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.1.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.47
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 (shmuel_nimi) than the most recent previously approved version (kalitas) on 2024-11-17, but shmuel_nimi 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.1.46
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 (shmuel_nimi) than the most recent previously approved version (kalitas) on 2024-11-17, but shmuel_nimi 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.1.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.43
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 (shmuel_nimi) than the most recent previously approved version (kalitas) on 2024-11-06, but shmuel_nimi 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.1.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.41
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 (shmuel_nimi) than the most recent previously approved version (kalitas) on 2024-11-03, but shmuel_nimi 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.1.40
2 findingsThis version was published by a different npm account than previous versions on 2024-11-03. 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.1.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.37
2 findingsThis version was published by a different npm account than previous versions on 2024-08-14. 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.1.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.