@remotion/eslint-config-flat
Default configuration for Remotion templates (ESLint >= 9)
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
Versions (showing 14 of 214)
| Version | Deps | Published |
|---|---|---|
| 4.0.293 | 1 / 6 | |
| 4.0.292 | 1 / 6 | |
| 4.0.291 | 1 / 6 | |
| 4.0.290 | 1 / 6 | |
| 4.0.289 | 1 / 6 | |
| 4.0.288 | 1 / 6 | |
| 4.0.287 | 1 / 6 | |
| 4.0.286 | 1 / 6 | |
| 4.0.285 | 1 / 6 | |
| 4.0.284 | 1 / 6 | |
| 4.0.282 | 1 / 6 | |
| 4.0.280 | 1 / 6 | |
| 4.0.279 | 1 / 6 | |
| 4.0.278 | 1 / 6 |
v4.0.291
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.290
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.289
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.288
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.287
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.286
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.285
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.284
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.282
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.280
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.279
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.278
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.