@rip-lang/csv
Fast, flexible CSV parser and writer for Rip - indexOf ratchet engine, auto-detection, zero dependencies
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @rip-lang/csv; edit-distance to 'qs' is a heuristic false positive for this namespace. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped package @rip-lang/csv; edit-distance to 'ajv' is a heuristic false positive for this namespace. | ai | |
| phantom-deps | phantom-dep:rip-lang | AI (phantom-deps): rip-lang is the runtime engine; csv.rip files are interpreted by it, not imported via JS require/import. | ai |
Versions (showing 100 of 134)
| Version | Deps | Published |
|---|---|---|
| 1.3.121 | 1 / 0 | |
| 1.3.120 | 1 / 0 | |
| 1.3.119 | 1 / 0 | |
| 1.3.118 | 1 / 0 | |
| 1.3.117 | 1 / 0 | |
| 1.3.116 | 1 / 0 | |
| 1.3.115 | 1 / 0 | |
| 1.3.114 | 1 / 0 | |
| 1.3.113 | 1 / 0 | |
| 1.3.112 | 1 / 0 | |
| 1.3.111 | 1 / 0 | |
| 1.3.110 | 1 / 0 | |
| 1.3.109 | 1 / 0 | |
| 1.3.108 | 1 / 0 | |
| 1.3.107 | 1 / 0 | |
| 1.3.106 | 1 / 0 | |
| 1.3.105 | 1 / 0 | |
| 1.3.104 | 1 / 0 | |
| 1.3.103 | 1 / 0 | |
| 1.3.102 | 1 / 0 | |
| 1.3.101 | 1 / 0 | |
| 1.3.100 | 1 / 0 | |
| 1.3.99 | 1 / 0 | |
| 1.3.98 | 1 / 0 | |
| 1.3.97 | 1 / 0 | |
| 1.3.96 | 1 / 0 | |
| 1.3.95 | 1 / 0 | |
| 1.3.94 | 1 / 0 | |
| 1.3.93 | 1 / 0 | |
| 1.3.92 | 1 / 0 | |
| 1.3.91 | 1 / 0 | |
| 1.3.90 | 1 / 0 | |
| 1.3.89 | 1 / 0 | |
| 1.3.88 | 1 / 0 | |
| 1.3.87 | 1 / 0 | |
| 1.3.86 | 1 / 0 | |
| 1.3.85 | 1 / 0 | |
| 1.3.84 | 1 / 0 | |
| 1.3.83 | 1 / 0 | |
| 1.3.82 | 1 / 0 | |
| 1.3.81 | 1 / 0 | |
| 1.3.80 | 1 / 0 | |
| 1.3.79 | 1 / 0 | |
| 1.3.78 | 1 / 0 | |
| 1.3.77 | 1 / 0 | |
| 1.3.76 | 1 / 0 | |
| 1.3.75 | 1 / 0 | |
| 1.3.74 | 1 / 0 | |
| 1.3.73 | 1 / 0 | |
| 1.3.72 | 1 / 0 | |
| 1.3.71 | 1 / 0 | |
| 1.3.70 | 1 / 0 | |
| 1.3.69 | 1 / 0 | |
| 1.3.68 | 1 / 0 | |
| 1.3.67 | 1 / 0 | |
| 1.3.66 | 1 / 0 | |
| 1.3.65 | 1 / 0 | |
| 1.3.64 | 1 / 0 | |
| 1.3.63 | 1 / 0 | |
| 1.3.62 | 1 / 0 | |
| 1.3.61 | 1 / 0 | |
| 1.3.60 | 1 / 0 | |
| 1.3.59 | 1 / 0 | |
| 1.3.58 | 1 / 0 | |
| 1.3.57 | 1 / 0 | |
| 1.3.56 | 1 / 0 | |
| 1.3.55 | 1 / 0 | |
| 1.3.54 | 1 / 0 | |
| 1.3.53 | 1 / 0 | |
| 1.3.52 | 1 / 0 | |
| 1.3.51 | 1 / 0 | |
| 1.3.50 | 1 / 0 | |
| 1.3.49 | 1 / 0 | |
| 1.3.48 | 1 / 0 | |
| 1.3.47 | 1 / 0 | |
| 1.3.46 | 1 / 0 | |
| 1.3.45 | 1 / 0 | |
| 1.3.44 | 1 / 0 | |
| 1.3.43 | 1 / 0 | |
| 1.3.42 | 1 / 0 | |
| 1.3.41 | 1 / 0 | |
| 1.3.40 | 1 / 0 | |
| 1.3.39 | 1 / 0 | |
| 1.3.38 | 1 / 0 | |
| 1.3.37 | 1 / 0 | |
| 1.3.36 | 1 / 0 | |
| 1.3.34 | 1 / 0 | |
| 1.3.33 | 1 / 0 | |
| 1.3.32 | 1 / 0 | |
| 1.3.31 | 1 / 0 | |
| 1.3.30 | 1 / 0 | |
| 1.3.29 | 1 / 0 | |
| 1.3.28 | 1 / 0 | |
| 1.3.27 | 1 / 0 | |
| 1.3.26 | 1 / 0 | |
| 1.3.24 | 1 / 0 | |
| 1.3.23 | 1 / 0 | |
| 1.3.22 | 1 / 0 | |
| 1.3.21 | 1 / 0 | |
| 1.3.20 | 1 / 0 |
v1.3.120
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.119
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.118
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.117
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.116
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.115
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.114
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.113
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.112
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.111
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.110
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.109
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.108
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.107
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.106
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.104
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.