babel-plugin-react-docgen
Babel plugin to add react-docgen info into your code
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate transition within Storybook org; shilman is a core Storybook maintainer with extensive track record. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Standard plugin-loading pattern: loads user-configured react-docgen handlers by name. Intentional API design. | ai | |
| provenance | no-provenance | AI (provenance): Published in 2020 before provenance attestations were standard practice. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 4.2.1 | 3 / 11 | |
| 4.2.0 | 3 / 10 | |
| 4.1.0 | 3 / 10 | |
| 4.0.0 | 3 / 10 | |
| 3.2.0 | 3 / 9 | |
| 3.1.0 | 3 / 9 | |
| 3.0.0 | 3 / 8 | |
| 2.0.2 | 3 / 8 | |
| 2.0.1 | 2 / 9 | |
| 2.0.0 | 2 / 9 | |
| 1.9.0 | 3 / 6 | |
| 1.8.3 | 3 / 5 | |
| 1.8.2 | 3 / 5 | |
| 1.8.1 | 3 / 5 | |
| 1.8.0 | 3 / 5 | |
| 1.7.0 | 3 / 5 | |
| 1.6.0 | 3 / 5 | |
| 1.5.0 | 3 / 5 | |
| 1.4.2 | 3 / 5 | |
| 1.4.1 | 3 / 5 | |
| 1.4.0 | 3 / 5 | |
| 1.3.2 | 4 / 4 | |
| 1.3.1 | 4 / 4 | |
| 1.3.0 | 4 / 4 | |
| 1.2.0 | 4 / 4 |
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
2 findingsThis version was published by a different npm account than previous versions on 2020-09-23. 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.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
2 findingsThis version was published by a different npm account than previous versions on 2020-01-02. 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.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.