← Home

prop-types-exact

npm Repository Homepage

For use with React PropTypes. Will error on any prop not explicitly specified.

12
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

lencioniljharb

Keywords

reactpropTypesproptypesvalidatorvalidationexact

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): lencioni is a known open-source contributor associated with the Airbnb ecosystem; addition is consistent with legitimate project maintenance by ljharb. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of airbnb org account is consistent with ljharb taking full ownership of this originally Airbnb-affiliated package; not a suspicious takeover. ai
publish-pattern new-deps-added AI (publish-pattern): es-errors, hasown, and isarray are well-known ljharb-ecosystem packages replacing the deprecated 'has' dep; standard modernization pattern, not suspicious. ai

Versions (showing 12 of 12)

Version Deps Published
1.2.7 6 / 17
1.2.6 6 / 17
1.2.5 6 / 16
1.2.4 5 / 16
1.2.3 5 / 16
1.2.2 5 / 16
1.2.1 5 / 22
1.2.0 3 / 17
1.1.2 2 / 19
1.1.1 2 / 19
1.1.0 3 / 19
1.0.0 2 / 18

v1.2.7

1 finding
LOW No provenance attestation provenance

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

v1.2.6

1 finding
LOW No provenance attestation provenance

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

v1.2.5

1 finding
LOW No provenance attestation provenance

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

v1.2.4

1 finding
LOW No provenance attestation provenance

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

v1.2.3

1 finding
LOW No provenance attestation provenance

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

v1.2.2

1 finding
LOW No provenance attestation provenance

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

v1.2.1

1 finding
LOW No provenance attestation provenance

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

v1.2.0

1 finding
LOW No provenance attestation provenance

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

v1.1.2

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.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.