@dynatrace/react-native-plugin
This plugin gives you the ability to use the Dynatrace Mobile agent in your react native application.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:proxy-polyfill | AI (dependencies): proxy-polyfill is a well-known Google-maintained polyfill; appropriate for this React Native plugin. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): safeRequire wrapper for optional module loading; stable pattern across versions of this package. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 2.343.1 | 5 / 47 | |
| 2.341.1 | 5 / 47 | |
| 2.339.1 | 5 / 47 | |
| 2.337.3 | 5 / 47 | |
| 2.337.2 | 5 / 47 | |
| 2.337.1 | 5 / 47 | |
| 2.335.1 | 5 / 46 | |
| 2.333.1 | 5 / 46 | |
| 2.331.1 | 5 / 42 | |
| 2.329.1 | 5 / 42 | |
| 2.327.2 | 5 / 40 | |
| 2.327.1 | 5 / 40 | |
| 2.325.2 | 5 / 40 | |
| 2.325.1 | 5 / 40 | |
| 2.323.2 | 5 / 38 | |
| 2.323.1 | 5 / 38 | |
| 2.321.2 | 5 / 37 | |
| 2.321.1 | 5 / 37 | |
| 2.319.1 | 5 / 42 | |
| 2.317.2 | 5 / 42 | |
| 2.317.1 | 5 / 42 | |
| 2.313.1 | 5 / 39 | |
| 2.307.1 | 5 / 39 | |
| 2.305.1 | 5 / 39 | |
| 2.303.2 | 5 / 39 | |
| 2.303.1 | 5 / 39 | |
| 2.301.2 | 5 / 39 | |
| 2.301.1 | 5 / 38 | |
| 2.299.1 | 5 / 38 | |
| 2.297.2 | 5 / 38 | |
| 2.297.1 | 5 / 38 | |
| 2.295.1 | 5 / 38 | |
| 2.293.2 | 5 / 38 | |
| 2.293.1 | 5 / 38 | |
| 2.291.2 | 5 / 38 | |
| 2.291.1 | 5 / 38 |
v2.343.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.341.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.339.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.307.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.305.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.303.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.303.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.301.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.301.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.299.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.297.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.297.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.295.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.293.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.293.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.291.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.291.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.