@djangocfg/typescript-config
Shared TypeScript configurations for Next.js, React libraries, and Node.js projects with strict type checking
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 51 of 515)
| Version | Deps | Published |
|---|---|---|
| 2.1.490 | 0 / 0 | |
| 2.1.489 | 0 / 0 | |
| 2.1.488 | 0 / 0 | |
| 2.1.487 | 0 / 0 | |
| 2.1.486 | 0 / 0 | |
| 2.1.484 | 0 / 0 | |
| 2.1.483 | 0 / 0 | |
| 2.1.482 | 0 / 0 | |
| 2.1.481 | 0 / 0 | |
| 2.1.480 | 0 / 0 | |
| 2.1.479 | 0 / 0 | |
| 2.1.478 | 0 / 0 | |
| 2.1.477 | 0 / 0 | |
| 2.1.476 | 0 / 0 | |
| 2.1.475 | 0 / 0 | |
| 2.1.474 | 0 / 0 | |
| 2.1.472 | 0 / 0 | |
| 2.1.471 | 0 / 0 | |
| 2.1.470 | 0 / 0 | |
| 2.1.469 | 0 / 0 | |
| 2.1.468 | 0 / 0 | |
| 2.1.466 | 0 / 0 | |
| 2.1.465 | 0 / 0 | |
| 2.1.464 | 0 / 0 | |
| 2.1.463 | 0 / 0 | |
| 2.1.462 | 0 / 0 | |
| 2.1.460 | 0 / 0 | |
| 2.1.459 | 0 / 0 | |
| 2.1.457 | 0 / 0 | |
| 2.1.456 | 0 / 0 | |
| 2.1.455 | 0 / 0 | |
| 2.1.454 | 0 / 0 | |
| 2.1.453 | 0 / 0 | |
| 2.1.452 | 0 / 0 | |
| 2.1.450 | 0 / 0 | |
| 2.1.449 | 0 / 0 | |
| 2.1.448 | 0 / 0 | |
| 2.1.447 | 0 / 0 | |
| 2.1.446 | 0 / 0 | |
| 2.1.445 | 0 / 0 | |
| 2.1.444 | 0 / 0 | |
| 2.1.443 | 0 / 0 | |
| 2.1.442 | 0 / 0 | |
| 2.1.441 | 0 / 0 | |
| 2.1.440 | 0 / 0 | |
| 2.1.439 | 0 / 0 | |
| 2.1.438 | 0 / 0 | |
| 2.1.437 | 0 / 0 | |
| 2.1.436 | 0 / 0 | |
| 2.1.435 | 0 / 0 | |
| 2.1.434 | 0 / 0 |
v2.1.490
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.489
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.488
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.487
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.486
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.484
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.483
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.482
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.481
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.480
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.479
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.478
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.477
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.476
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.475
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.474
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.472
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.471
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.470
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.469
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.468
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.466
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.465
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.464
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.463
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.462
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.460
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.459
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.457
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.456
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.455
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.454
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.453
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.452
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.450
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.449
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.448
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.447
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.446
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.445
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.444
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.443
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.442
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.441
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.