@sentry-internal/eslint-config-sdk
Official Sentry SDK eslint config
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:eslint-plugin-jsdoc | AI (phantom-deps): ESLint config packages reference plugins in config objects, not via require/import; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-import | AI (phantom-deps): Same as above — config-only reference, not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:eslint-config-prettier | AI (phantom-deps): Config-only reference; expected pattern for eslint-config packages. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/parser | AI (phantom-deps): Config-only reference; expected pattern for eslint-config packages. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-deprecation | AI (phantom-deps): Config-only reference; expected pattern for eslint-config packages. | ai | |
| phantom-deps | phantom-dep:@sentry-internal/typescript | AI (phantom-deps): Same-org dep referenced in config; not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/eslint-plugin | AI (phantom-deps): Config-only reference; expected pattern for eslint-config packages. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-simple-import-sort | AI (phantom-deps): Config-only reference; expected pattern for eslint-config packages. | ai | |
| phantom-deps | phantom-dep:@sentry-internal/eslint-plugin-sdk | AI (phantom-deps): Same-org dep referenced in config; not a real phantom dep. | ai |
Versions (showing 51 of 62)
| Version | Deps | Published |
|---|---|---|
| 10.55.0 | 9 / 1 | |
| 10.54.0 | 9 / 1 | |
| 10.53.1 | 9 / 1 | |
| 10.53.0 | 9 / 1 | |
| 10.52.0 | 9 / 1 | |
| 10.51.0 | 9 / 1 | |
| 10.50.0 | 9 / 1 | |
| 10.49.0 | 9 / 1 | |
| 10.48.0 | 9 / 1 | |
| 10.47.0 | 9 / 1 | |
| 10.46.0 | 9 / 1 | |
| 10.45.0 | 9 / 1 | |
| 10.44.0 | 9 / 1 | |
| 10.43.0 | 9 / 1 | |
| 10.42.0 | 9 / 1 | |
| 10.41.0 | 9 / 1 | |
| 10.40.0 | 9 / 1 | |
| 10.39.0 | 9 / 1 | |
| 10.38.0 | 9 / 1 | |
| 10.37.0 | 9 / 1 | |
| 10.36.0 | 9 / 1 | |
| 10.35.0 | 9 / 1 | |
| 10.34.0 | 9 / 1 | |
| 10.33.0 | 9 / 1 | |
| 10.32.1 | 9 / 1 | |
| 10.32.0 | 9 / 1 | |
| 10.31.0 | 9 / 1 | |
| 10.30.0 | 9 / 1 | |
| 10.29.0 | 9 / 1 | |
| 10.28.0 | 9 / 1 | |
| 10.27.0 | 9 / 1 | |
| 10.26.0 | 9 / 1 | |
| 10.25.0 | 9 / 1 | |
| 10.24.0 | 9 / 1 | |
| 10.23.0 | 9 / 1 | |
| 10.22.0 | 9 / 1 | |
| 10.21.0 | 9 / 1 | |
| 10.20.0 | 9 / 1 | |
| 10.19.0 | 9 / 1 | |
| 10.18.0 | 9 / 1 | |
| 10.17.0 | 9 / 1 | |
| 10.16.0 | 9 / 1 | |
| 10.15.0 | 9 / 1 | |
| 10.14.0 | 9 / 1 | |
| 10.13.0 | 9 / 1 | |
| 10.12.0 | 9 / 1 | |
| 10.11.0 | 9 / 1 | |
| 10.10.0 | 9 / 1 | |
| 10.9.0 | 9 / 1 | |
| 10.8.0 | 9 / 1 | |
| 10.7.0 | 9 / 1 |
v10.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.53.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.51.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.50.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.32.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.