@tsparticles/basic
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher moved to GitHub Actions CI/CD with SLSA provenance; legitimate automation transition. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Same-org deps replacing removed ones in a major version bump; internal refactor. | ai | |
| dependencies | unvetted-dep:@tsparticles/move-base | AI (dependencies): First-party sibling package from the same tsparticles monorepo and publisher. | ai | |
| dependencies | unvetted-dep:@tsparticles/shape-circle | AI (dependencies): First-party sibling package from the same tsparticles monorepo and publisher. | ai | |
| dependencies | unvetted-dep:@tsparticles/updater-size | AI (dependencies): First-party sibling package from the same tsparticles monorepo and publisher. | ai | |
| dependencies | unvetted-dep:@tsparticles/updater-color | AI (dependencies): First-party sibling package from the same tsparticles monorepo and publisher. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval calls are webpack devtool bundle artifacts, not dynamic user input; stable pattern across all tsparticles bundle packages. | ai | |
| dependencies | unvetted-dep:@tsparticles/plugin-hex-color | AI (dependencies): First-party sibling package from the same tsparticles monorepo and publisher. | ai | |
| dependencies | unvetted-dep:@tsparticles/plugin-hsl-color | AI (dependencies): First-party sibling package from the same tsparticles monorepo and publisher. | ai | |
| dependencies | unvetted-dep:@tsparticles/plugin-rgb-color | AI (dependencies): First-party sibling package from the same tsparticles monorepo and publisher. | ai | |
| dependencies | unvetted-dep:@tsparticles/updater-out-modes | AI (dependencies): First-party sibling package from the same tsparticles monorepo and publisher. | ai | |
| dependencies | unvetted-dep:@tsparticles/updater-opacity | AI (dependencies): First-party sibling package from the same tsparticles monorepo and publisher. | ai | |
| dependencies | unvetted-dep:@tsparticles/engine | AI (dependencies): First-party sibling package from the same tsparticles monorepo and publisher. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 4.1.3 | 11 / 0 | |
| 4.1.2 | 11 / 0 | |
| 4.1.1 | 11 / 0 | |
| 4.1.0 | 11 / 0 | |
| 4.0.5 | 11 / 0 | |
| 4.0.4 | 11 / 0 | |
| 4.0.3 | 11 / 0 | |
| 4.0.2 | 10 / 0 | |
| 4.0.1 | 10 / 0 | |
| 4.0.0 | 10 / 0 | |
| 3.9.1 | 10 / 0 | |
| 3.9.0 | 10 / 0 |
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
2 findingsThis version was published by a different npm account than previous versions on 2026-05-19. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.4
2 findingsThis version was published by a different npm account than previous versions on 2026-05-19. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.3
2 findingsThis version was published by a different npm account than previous versions on 2026-05-18. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.2
2 findingsThis version was published by a different npm account than previous versions on 2026-05-16. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.1
2 findingsThis version was published by a different npm account than previous versions on 2026-05-16. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-15. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.