@getpaseo/highlight
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): @replit/codemirror-lang-csharp is a legitimate CodeMirror language extension; addition is consistent with package purpose. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across all versions; internal scoped package pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped internal package; missing metadata is a style choice, not malicious. | ai | |
| dependencies | unvetted-dep:@lezer/json | AI (dependencies): @lezer/json is a well-known CodeMirror/Lezer parser; stable false positive for this syntax-highlighting package. | ai |
Versions (showing 60 of 60)
| Version | Deps | Published |
|---|---|---|
| 0.2.3 | 19 / 2 | |
| 0.2.0 | 19 / 2 | |
| 0.1.109 | 19 / 2 | |
| 0.1.108 | 19 / 2 | |
| 0.1.107 | 19 / 2 | |
| 0.1.106 | 19 / 2 | |
| 0.1.105 | 19 / 2 | |
| 0.1.104 | 19 / 2 | |
| 0.1.102 | 19 / 2 | |
| 0.1.101 | 18 / 2 | |
| 0.1.100 | 18 / 2 | |
| 0.1.99 | 18 / 2 | |
| 0.1.98 | 18 / 2 | |
| 0.1.97 | 18 / 2 | |
| 0.1.96 | 18 / 2 | |
| 0.1.95 | 18 / 2 | |
| 0.1.94 | 18 / 2 | |
| 0.1.93 | 18 / 2 | |
| 0.1.92 | 18 / 2 | |
| 0.1.91 | 18 / 2 | |
| 0.1.90 | 18 / 2 | |
| 0.1.89 | 18 / 2 | |
| 0.1.88 | 18 / 2 | |
| 0.1.87 | 16 / 2 | |
| 0.1.86 | 16 / 2 | |
| 0.1.85 | 16 / 2 | |
| 0.1.84 | 16 / 2 | |
| 0.1.83 | 16 / 2 | |
| 0.1.82 | 16 / 2 | |
| 0.1.81 | 16 / 2 | |
| 0.1.80 | 16 / 2 | |
| 0.1.79 | 16 / 2 | |
| 0.1.63 | 16 / 2 | |
| 0.1.62 | 16 / 2 | |
| 0.1.61 | 16 / 2 | |
| 0.1.60 | 16 / 2 | |
| 0.1.59 | 16 / 2 | |
| 0.1.58 | 16 / 2 | |
| 0.1.57 | 16 / 2 | |
| 0.1.56 | 16 / 2 | |
| 0.1.55 | 16 / 2 | |
| 0.1.54 | 16 / 2 | |
| 0.1.53 | 16 / 2 | |
| 0.1.52 | 16 / 2 | |
| 0.1.50 | 16 / 2 | |
| 0.1.49 | 16 / 2 | |
| 0.1.48 | 16 / 2 | |
| 0.1.47 | 16 / 2 | |
| 0.1.46 | 16 / 2 | |
| 0.1.45 | 16 / 2 | |
| 0.1.44 | 16 / 2 | |
| 0.1.43 | 16 / 2 | |
| 0.1.42 | 16 / 2 | |
| 0.1.41 | 16 / 2 | |
| 0.1.40 | 16 / 2 | |
| 0.1.38 | 16 / 2 | |
| 0.1.37 | 16 / 2 | |
| 0.1.35 | 16 / 2 | |
| 0.1.34 | 16 / 2 | |
| 0.1.32 | 16 / 2 |
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.109
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.108
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.107
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.106
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.104
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.