@wisemen/eslint-config-nestjs
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:@typescript-eslint/eslint-plugin | AI (phantom-deps): ESLint plugin referenced in config files; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@eslint/js | AI (phantom-deps): Framework-scoped ESLint package loaded by convention in config packages. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-unicorn | AI (phantom-deps): ESLint plugin referenced in config files; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-import-typescript | AI (phantom-deps): ESLint plugin referenced in config files; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:oxfmt | AI (phantom-deps): ESLint config packages reference tools by convention; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:oxlint | AI (phantom-deps): ESLint config packages reference tools by convention; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Type-only package loaded by convention in Node.js tooling configs. | ai | |
| phantom-deps | phantom-dep:@eslint/eslintrc | AI (phantom-deps): ESLint framework-scoped package loaded by convention in ESLint configs. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): ESLint config package; typescript is a peer/tooling dep loaded by convention, not directly imported. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 1.1.1 | 16 / 0 | |
| 1.1.0 | 15 / 0 | |
| 1.0.0 | 14 / 0 | |
| 0.2.13 | 12 / 0 | |
| 0.2.12 | 12 / 0 | |
| 0.2.11 | 12 / 0 | |
| 0.2.10 | 12 / 0 | |
| 0.2.9 | 12 / 0 | |
| 0.2.8 | 12 / 0 | |
| 0.2.7 | 12 / 0 | |
| 0.2.6 | 10 / 0 | |
| 0.2.5 | 10 / 0 | |
| 0.2.4 | 10 / 0 | |
| 0.2.3 | 10 / 0 | |
| 0.2.2 | 10 / 0 | |
| 0.2.1 | 10 / 0 | |
| 0.1.10 | 10 / 0 | |
| 0.1.9 | 10 / 0 | |
| 0.1.8 | 10 / 0 |
v1.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.