@babel/plugin-transform-object-rest-spread
Compile object rest and spread to ES5
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@babel/plugin-transform-parameters | AI (dependencies): @babel/plugin-transform-parameters is an official Babel package; its use as a dependency here is expected and legitimate for this plugin. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 7.29.7 | 5 / 3 | |
| 7.28.6 | 5 / 3 | |
| 7.28.4 | 5 / 3 | |
| 7.28.0 | 5 / 3 | |
| 7.27.7 | 5 / 3 | |
| 7.27.3 | 4 / 3 | |
| 7.27.2 | 4 / 3 | |
| 7.27.1 | 3 / 3 | |
| 7.25.9 | 3 / 3 | |
| 7.25.8 | 3 / 3 | |
| 7.25.7 | 4 / 3 | |
| 7.24.7 | 4 / 3 | |
| 7.24.6 | 4 / 3 | |
| 7.24.5 | 4 / 3 | |
| 7.24.1 | 4 / 3 | |
| 7.24.0 | 5 / 3 | |
| 7.23.4 | 5 / 3 | |
| 7.23.3 | 5 / 3 | |
| 7.22.15 | 5 / 3 | |
| 7.22.11 | 5 / 3 | |
| 7.22.5 | 5 / 3 | |
| 7.22.3 | 5 / 3 | |
| 7.22.0 | 5 / 3 |
v7.29.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.28.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.27.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.27.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.27.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.27.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.25.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.25.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.25.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.24.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.24.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.24.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.23.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.23.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.22.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.