@keyvhq/offline
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get used in a Proxy handler for method delegation — standard JS pattern, not obfuscation. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 2.2.3 | 2 / 5 | |
| 2.2.0 | 2 / 5 | |
| 2.1.17 | 2 / 5 | |
| 2.1.15 | 2 / 5 | |
| 2.1.14 | 2 / 5 | |
| 2.1.13 | 2 / 5 | |
| 2.1.12 | 2 / 5 | |
| 2.1.11 | 2 / 5 | |
| 2.1.10 | 2 / 5 | |
| 2.1.8 | 2 / 5 | |
| 2.1.7 | 2 / 5 | |
| 2.1.5 | 2 / 5 | |
| 2.1.1 | 2 / 5 | |
| 2.0.3 | 2 / 5 | |
| 2.0.0 | 2 / 6 |
v2.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.