@tailwindcss/oxide
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): tar and detect-libc are expected dependencies for napi-rs prebuilt binary installation. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): napi-rs prebuilt binary installer; stable pattern for this native binding package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer removal reflects internal Tailwind Labs team restructuring, not a hostile takeover. SLSA provenance confirms CI/CD-published release. | ai | |
| provenance | publisher-changed | AI (provenance): malfaitrobin (Robin Malfait) is a known Tailwind Labs core team member; publisher transition is legitimate and covered by SLSA provenance attestation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy aligns with Tailwind CSS v4 development cycle. SLSA provenance attestation and known publisher identity rule out account takeover. | ai | |
| semgrep | semgrep:child-process-execsync | AI (semgrep): Hardcoded 'ldd --version' call for musl detection in napi-rs binary selection logic. Not user-controlled; stable false positive for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): napi-rs documented escape hatch via NAPI_RS_NATIVE_LIBRARY_PATH env var for custom native library paths. Expected pattern for this package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): napi-rs pattern: execSync('ldd --version') is a hardcoded musl detection call, not arbitrary command execution. Stable and expected for this native binding package. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 4.3.0 | 0 / 3 | |
| 4.2.4 | 0 / 3 | |
| 4.2.3 | 0 / 3 | |
| 4.2.2 | 0 / 3 | |
| 4.2.1 | 0 / 3 | |
| 4.2.0 | 0 / 3 | |
| 4.1.18 | 0 / 3 | |
| 4.1.17 | 0 / 3 | |
| 4.1.16 | 0 / 3 | |
| 4.1.15 | 0 / 3 | |
| 4.1.14 | 2 / 3 | |
| 4.1.13 | 2 / 3 | |
| 4.1.12 | 2 / 3 | |
| 4.1.10 | 2 / 3 | |
| 4.1.9 | 2 / 3 | |
| 4.1.8 | 2 / 3 | |
| 4.1.6 | 2 / 3 | |
| 4.1.5 | 0 / 3 |
v4.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-23. 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.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.14
2 findingsScript: node ./scripts/install.js
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.13
2 findingsScript: node ./scripts/install.js
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.12
2 findingsScript: node ./scripts/install.js
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.10
2 findingsScript: node ./scripts/install.js
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.9
2 findingsScript: node ./scripts/install.js
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.8
2 findingsScript: node ./scripts/install.js
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.6
2 findingsScript: node ./scripts/install.js
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.