eslint-config-txo-typescript
Technology Studio - Eslint typescript config
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:eslint-plugin-n | AI (phantom-deps): ESLint config packages reference plugins in config files, not code imports; stable pattern. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-promise | AI (phantom-deps): ESLint config packages reference plugins in config files, not code imports; stable pattern. | ai | |
| phantom-deps | phantom-dep:eslint-import-resolver-typescript | AI (phantom-deps): ESLint config packages reference plugins in config files, not code imports; stable pattern. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 7.4.115 | 13 / 13 | |
| 7.4.114 | 13 / 13 | |
| 7.4.113 | 13 / 13 | |
| 7.4.112 | 13 / 13 | |
| 7.4.111 | 13 / 13 | |
| 7.4.110 | 13 / 13 | |
| 7.4.109 | 13 / 11 | |
| 7.4.108 | 13 / 11 | |
| 7.4.107 | 13 / 11 | |
| 7.4.106 | 13 / 11 | |
| 7.4.105 | 13 / 11 | |
| 7.4.104 | 13 / 11 | |
| 7.4.103 | 13 / 11 | |
| 7.4.102 | 13 / 11 | |
| 7.4.101 | 13 / 11 | |
| 7.4.100 | 13 / 11 | |
| 7.4.99 | 13 / 11 | |
| 7.4.98 | 13 / 11 | |
| 7.4.97 | 13 / 11 | |
| 7.4.96 | 13 / 11 | |
| 7.4.95 | 13 / 11 | |
| 7.4.94 | 13 / 11 | |
| 7.4.93 | 13 / 11 | |
| 7.4.92 | 13 / 11 | |
| 7.4.91 | 13 / 11 | |
| 7.4.90 | 13 / 11 | |
| 7.4.89 | 13 / 11 | |
| 7.4.88 | 13 / 11 | |
| 7.4.87 | 13 / 11 | |
| 7.4.86 | 13 / 11 | |
| 7.4.85 | 13 / 11 | |
| 7.4.84 | 13 / 11 | |
| 7.4.83 | 13 / 11 | |
| 7.4.82 | 13 / 11 | |
| 7.4.81 | 13 / 11 | |
| 7.4.80 | 13 / 11 | |
| 7.4.79 | 13 / 11 | |
| 7.4.78 | 13 / 11 | |
| 7.4.77 | 13 / 11 | |
| 7.4.76 | 13 / 11 | |
| 7.4.75 | 13 / 11 | |
| 7.4.74 | 13 / 11 | |
| 7.4.73 | 13 / 11 | |
| 7.4.72 | 13 / 11 |
v7.4.115
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.4.114
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.4.113
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.112
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.111
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.110
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.109
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.108
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.107
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.106
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.104
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.