@tsparticles/eslint-config
tsParticles default ESLint Configuration (ESLint 10 + Flat 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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Package has SLSA provenance attestation; missing gitHead is a minor metadata gap, not a supply chain risk for this org. | ai | |
| provenance | slsa-provenance | AI (provenance): Package consistently publishes via GitHub Actions with SLSA/Sigstore attestation; this is the expected and documented publish flow for the tsparticles ecosystem. | ai | |
| dependencies | unvetted-dep:prettier-plugin-multiline-arrays | AI (dependencies): Legitimate Prettier plugin; expected dependency for an ESLint/Prettier config package. | ai | |
| phantom-deps | phantom-dep:jiti | AI (phantom-deps): ESLint flat config packages reference tools like jiti in config files rather than direct imports; this is a known pattern, not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:prettier | AI (phantom-deps): Prettier is referenced in ESLint config files, not via direct imports; standard pattern for ESLint/Prettier config packages. | ai | |
| dependencies | unvetted-dep:eslint-plugin-tsdoc | AI (dependencies): eslint-plugin-tsdoc is a legitimate, well-known ESLint plugin; expected dependency for an ESLint config package. | ai | |
| phantom-deps | phantom-dep:@tsparticles/prettier-config | AI (phantom-deps): Same-org package referenced in config files; expected pattern for this type of config package. | ai | |
| phantom-deps | phantom-dep:prettier-plugin-multiline-arrays | AI (phantom-deps): Prettier plugin referenced in config files rather than direct imports; standard pattern for ESLint/Prettier config packages. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): TypeScript is referenced in ESLint config files for typescript-eslint integration; standard pattern, not a real phantom dep. | ai | |
| dependencies | unvetted-dep:@tsparticles/prettier-config | AI (dependencies): Same-org prettier config package; expected and appropriate dependency for this ESLint config package. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 4.1.3 | 12 / 2 | |
| 4.1.2 | 12 / 2 | |
| 4.1.1 | 12 / 2 | |
| 4.1.0 | 12 / 2 | |
| 4.0.5 | 12 / 2 | |
| 4.0.4 | 12 / 2 | |
| 4.0.3 | 12 / 2 | |
| 4.0.2 | 12 / 2 | |
| 4.0.1 | 12 / 2 | |
| 4.0.0 | 12 / 2 | |
| 3.4.14 | 12 / 2 | |
| 3.4.13 | 12 / 2 | |
| 3.4.12 | 12 / 2 | |
| 3.4.11 | 12 / 2 | |
| 3.4.10 | 12 / 2 | |
| 3.4.9 | 12 / 2 | |
| 3.4.7 | 12 / 2 | |
| 3.4.6 | 12 / 2 | |
| 3.4.5 | 12 / 2 | |
| 3.4.4 | 12 / 2 | |
| 3.4.3 | 12 / 2 | |
| 3.4.2 | 12 / 2 | |
| 3.4.1 | 12 / 2 | |
| 3.1.1 | 0 / 14 | |
| 3.1.0 | 0 / 12 | |
| 3.0.13 | 0 / 12 | |
| 3.0.12 | 0 / 12 | |
| 3.0.11 | 0 / 12 | |
| 3.0.10 | 0 / 12 | |
| 3.0.9 | 0 / 12 | |
| 3.0.7 | 0 / 12 | |
| 3.0.6 | 0 / 12 | |
| 3.0.5 | 0 / 12 | |
| 3.0.3 | 0 / 12 | |
| 3.0.2 | 0 / 12 | |
| 3.0.1 | 0 / 12 | |
| 3.0.0 | 0 / 12 |
v4.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.12
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.10
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.9
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.