react-number-format
React component to format number in an input or as a text.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:prop-types | AI (phantom-deps): Likely used via prop-types in build/dist output; common false positive for React component libs. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 5.4.5 | 0 / 54 | |
| 5.4.4 | 0 / 54 | |
| 5.4.3 | 0 / 54 | |
| 5.4.2 | 0 / 54 | |
| 5.4.1 | 0 / 54 | |
| 5.4.0 | 1 / 54 | |
| 5.3.4 | 1 / 66 | |
| 5.3.3 | 1 / 66 | |
| 5.3.2 | 1 / 66 | |
| 5.3.1 | 1 / 66 | |
| 5.3.0 | 1 / 66 | |
| 5.2.2 | 1 / 66 | |
| 5.2.0 | 1 / 66 | |
| 5.1.4 | 1 / 66 | |
| 5.1.3 | 1 / 66 | |
| 5.1.2 | 1 / 66 | |
| 5.1.1 | 1 / 66 | |
| 5.1.0 | 1 / 66 | |
| 5.0.1 | 1 / 66 | |
| 5.0.0 | 1 / 65 |
v5.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: sudhanshu.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.