@limetech/n8n-nodes-lime
n8n node to connect to Lime CRM
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Shift to GitHub Actions CI publishing is an improvement, not compromise indicator. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Standard crypto decrypt helper decoding base64 ciphertext, not payload obfuscation. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Diff spans many unimported intermediate npm versions; expected growth for this package. | ai | |
| phantom-deps | phantom-dep:request | AI (phantom-deps): request is a declared runtime dep used transitively; phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:@semantic-release/exec | AI (phantom-deps): semantic-release plugin referenced in release config, not directly imported in source — stable false positive. | ai | |
| phantom-deps | phantom-dep:request-promise-native | AI (phantom-deps): Declared runtime dep; phantom-dep fires because it's not directly imported in TS source — false positive. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 3.12.0 | 0 / 14 | |
| 3.11.3 | 0 / 14 | |
| 3.11.2 | 0 / 14 | |
| 3.11.1 | 0 / 14 | |
| 3.11.0 | 0 / 14 | |
| 3.10.3 | 0 / 14 | |
| 3.10.2 | 0 / 14 | |
| 3.10.1 | 0 / 14 | |
| 3.10.0 | 0 / 14 | |
| 3.9.0 | 0 / 14 | |
| 3.8.0 | 0 / 14 | |
| 3.7.1 | 0 / 14 | |
| 3.7.0 | 0 / 14 | |
| 3.6.3 | 0 / 14 | |
| 3.6.2 | 0 / 14 | |
| 3.6.1 | 0 / 14 | |
| 3.6.0 | 0 / 14 | |
| 3.5.2 | 0 / 14 | |
| 3.5.1 | 0 / 14 | |
| 3.5.0 | 0 / 14 | |
| 3.4.0 | 0 / 14 | |
| 3.3.0 | 0 / 14 | |
| 3.2.2 | 0 / 14 | |
| 3.2.1 | 0 / 14 | |
| 3.2.0 | 0 / 14 | |
| 3.1.0 | 0 / 14 | |
| 3.0.0 | 0 / 16 | |
| 2.6.1 | 2 / 17 | |
| 2.6.0 | 2 / 17 | |
| 2.5.5 | 2 / 17 | |
| 2.5.4 | 2 / 18 | |
| 2.5.3 | 2 / 18 | |
| 2.5.2 | 2 / 18 | |
| 2.5.1 | 2 / 18 | |
| 2.5.0 | 2 / 18 | |
| 0.5.0 | 6 / 25 |
v3.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.3
2 findingsThis version was published by a different npm account than previous versions on 2026-07-20. 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.
v3.11.2
2 findingsThis version was published by a different npm account than previous versions on 2026-07-08. 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.
v3.11.1
2 findingsThis version was published by a different npm account than previous versions on 2026-07-08. 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.
v3.11.0
2 findingsThis version was published by a different npm account than previous versions on 2026-07-07. 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.
v3.10.3
2 findingsThis version was published by a different npm account than previous versions on 2026-07-02. 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.