ast-walker-scope
Traverse Babel AST with scope information.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@babel/parser | AI (dependencies): @babel/parser is a core Babel ecosystem package with millions of weekly downloads; flagging it as unvetted is a stable false positive for any package depending on it. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.10.0 | 3 / 14 | |
| 0.9.0 | 3 / 14 | |
| 0.8.3 | 2 / 13 | |
| 0.8.2 | 2 / 13 | |
| 0.8.1 | 2 / 13 | |
| 0.8.0 | 2 / 13 | |
| 0.7.1 | 2 / 14 | |
| 0.7.0 | 2 / 14 | |
| 0.6.2 | 2 / 14 | |
| 0.6.1 | 2 / 14 | |
| 0.6.0 | 2 / 14 | |
| 0.5.0 | 2 / 15 | |
| 0.4.2 | 2 / 15 | |
| 0.4.1 | 2 / 15 | |
| 0.4.0 | 2 / 15 | |
| 0.3.1 | 2 / 15 | |
| 0.3.0 | 2 / 15 | |
| 0.2.3 | 2 / 15 | |
| 0.2.2 | 2 / 15 | |
| 0.2.1 | 2 / 15 | |
| 0.2.0 | 2 / 15 | |
| 0.1.0 | 2 / 15 |
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.