react-docgen-actual-name-handler
This is an internal docz [react-docgen](https://github.com/reactjs/react-docgen) [handler](https://github.com/reactjs/react-docgen#handlers) used to set `actualName` on React components.
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change from rakannimer to renatobenks reflects a legitimate maintainer transition within the Docz ecosystem; renatobenks is an established publisher with 313 approved packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer renatobenks is a known Docz ecosystem contributor with a clean track record; transition is consistent with the doczjs/docz repository ownership. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Package is a utility helper within the Docz monorepo; sparse README and no keywords are expected for an internal/utility package, not spam indicators. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 2.4.0 | 2 / 0 | |
| 2.1.0 | 2 / 2 | |
| 2.0.0 | 2 / 2 | |
| 1.2.0 | 2 / 2 | |
| 1.1.0 | 2 / 2 | |
| 1.0.4 | 2 / 1 | |
| 1.0.2 | 2 / 1 | |
| 1.0.1 | 2 / 1 | |
| 1.0.0 | 2 / 0 | |
| 0.13.5 | 2 / 0 |
v2.4.0
2 findingsThis version was published by a different npm account than previous versions on 2022-02-11. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: rakannimer.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-11-25. This could indicate a legitimate maintainer transition or an account compromise.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.