@tailwindcss/line-clamp
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | rapid-publish | AI (publish-pattern): Benign patch cadence from known maintainer, no malicious indicators. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): semver is a well-known, trusted dependency. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Growth reflects added semver-based logic, not injected payload. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Long-stable transition to known Tailwind org maintainer, not a takeover. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same legitimate Tailwind Labs maintainer transition. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.4.4 | 0 / 4 | |
| 0.4.3 | 1 / 4 | |
| 0.4.2 | 0 / 4 | |
| 0.4.1 | 0 / 4 | |
| 0.4.0 | 0 / 4 | |
| 0.3.1 | 0 / 0 | |
| 0.3.0 | 0 / 4 | |
| 0.2.2 | 0 / 4 | |
| 0.2.1 | 0 / 4 | |
| 0.2.0 | 0 / 4 | |
| 0.1.0 | 0 / 4 |
v0.4.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (malfaitrobin) than the most recent previously approved version (adamwathan) on 2023-03-30, but malfaitrobin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.4.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (bradlc) than the most recent previously approved version (adamwathan) on 2022-09-02, but bradlc is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.4.1
2 findingsThis version was published by a different npm account (thecrypticace) than the most recent previously approved version (adamwathan) on 2022-09-01. It has since remained available on npm for 1419 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
2 findingsThis version was published by a different npm account (thecrypticace) than the most recent previously approved version (adamwathan) on 2022-04-27. It has since remained available on npm for 1546 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (adamwathan) than the most recent previously approved version (malfaitrobin) on 2022-01-12, but adamwathan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.3.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (malfaitrobin) than the most recent previously approved version (reinink) on 2021-12-09, but malfaitrobin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.2.2
2 findingsThis version was published by a different npm account (reinink) than the most recent previously approved version (malfaitrobin) on 2021-10-01. It has since remained available on npm for 1754 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (adamwathan) than the most recent previously approved version (malfaitrobin) on 2021-05-24, but adamwathan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.