← Home

@tailwindcss/forms

npm Repository Homepage
26
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

reininkadamwathanmalfaitrobinthecrypticace

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:cors AI (typosquat): Official tailwindlabs scoped package; Levenshtein match to 'cors' is a false positive. ai

Versions (showing 26 of 26)

Version Deps Published
0.5.11 1 / 7
0.5.10 1 / 7
0.5.9 1 / 5
0.5.8 1 / 5
0.5.7 1 / 5
0.5.6 1 / 5
0.5.5 1 / 5
0.5.4 1 / 5
0.5.3 1 / 5
0.5.2 1 / 5
0.5.1 1 / 5
0.5.0 1 / 5
0.4.1 1 / 5
0.4.0 1 / 7
0.3.4 1 / 7
0.3.3 1 / 7
0.3.2 1 / 7
0.3.1 1 / 7
0.3.0 1 / 7
0.2.1 1 / 7
0.2.0 1 / 4
0.1.4 2 / 3
0.1.3 2 / 3
0.1.2 2 / 3
0.1.1 2 / 3
0.1.0 1 / 4

v0.5.10

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.5.9

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.5.8

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.5.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.4

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: malfaitrobin → thecrypticace (on 2023-07-13, known maintainer) provenance

This version was published by a different npm account (thecrypticace) than the most recent previously approved version (malfaitrobin) on 2023-07-13, but thecrypticace 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.5.3

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: malfaitrobin → bradlc (on 2022-09-02, known maintainer) provenance

This version was published by a different npm account (bradlc) than the most recent previously approved version (malfaitrobin) 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.5.2

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: thecrypticace → malfaitrobin (on 2022-05-18, known maintainer) provenance

This version was published by a different npm account (malfaitrobin) than the most recent previously approved version (thecrypticace) on 2022-05-18, 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.5.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.1

2 findings
MEDIUM Publisher changed: malfaitrobin → thecrypticace (on 2022-03-02, unremoved on npm for 1602d) provenance

This version was published by a different npm account (thecrypticace) than the most recent previously approved version (malfaitrobin) on 2022-03-02. It has since remained available on npm for 1602 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: reinink → malfaitrobin (on 2021-12-09, known maintainer) provenance

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.3.4

2 findings
MEDIUM Publisher changed: adamwathan → reinink (on 2021-09-28, unremoved on npm for 1757d) provenance

This version was published by a different npm account (reinink) than the most recent previously approved version (adamwathan) on 2021-09-28. It has since remained available on npm for 1757 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.