react-data-table-component
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/locales/index.js | AI (source-diff): Minified locale/i18n string bundle; no executable logic or network calls. Normal build output for this package. | ai | |
| source-diff | obfuscated-file:dist/locales/index.mjs | AI (source-diff): ESM variant of the same minified locale bundle; benign build artifact. | ai | |
| provenance | publisher-changed | AI (provenance): GitHub Actions publisher with SLSA provenance attestation is the expected CI/CD automation pattern; original author still in package.json. | ai | |
| source-diff | obfuscated-file:dist/index.js | AI (source-diff): Standard tsup minified bundle output; CSS class names and React patterns confirm legitimate component code. | ai | |
| source-diff | obfuscated-file:dist/index.mjs | AI (source-diff): ESM variant of the same tsup build; content is consistent with a React data table component. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 8.8.0 | 0 / 22 | |
| 8.7.1 | 0 / 22 | |
| 8.7.0 | 0 / 22 | |
| 8.6.2 | 0 / 22 | |
| 8.6.1 | 0 / 22 | |
| 8.6.0 | 0 / 22 | |
| 8.5.2 | 0 / 22 | |
| 8.5.1 | 0 / 22 | |
| 8.5.0 | 0 / 22 | |
| 8.4.3 | 0 / 22 | |
| 8.4.2 | 0 / 22 | |
| 8.4.1 | 0 / 22 | |
| 8.4.0 | 0 / 22 | |
| 8.3.0 | 0 / 22 | |
| 8.2.0 | 0 / 22 | |
| 8.1.0 | 0 / 22 | |
| 8.0.1 | 0 / 22 | |
| 8.0.0 | 0 / 21 | |
| 7.7.1 | 1 / 65 | |
| 7.7.0 | 1 / 64 |
v8.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.7.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.6.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.5.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.4.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.4.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.