@motech-development/webpack-permissions-plugin
A Webpack plugin to set permissions for your output files and folders
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:filehound | AI (dependencies): filehound is a legitimate file-search utility appropriate for a webpack permissions plugin; stable across versions. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 1.3.1 | 1 / 20 | |
| 1.3.0 | 2 / 30 | |
| 1.2.1 | 2 / 30 | |
| 1.2.0 | 2 / 29 | |
| 1.1.0 | 2 / 28 | |
| 1.0.28 | 2 / 27 | |
| 1.0.27 | 2 / 27 | |
| 1.0.26 | 2 / 27 | |
| 1.0.25 | 2 / 27 | |
| 1.0.24 | 2 / 27 | |
| 1.0.23 | 2 / 27 | |
| 1.0.22 | 2 / 27 | |
| 1.0.21 | 2 / 27 | |
| 1.0.20 | 2 / 27 | |
| 1.0.19 | 2 / 27 | |
| 1.0.18 | 2 / 27 | |
| 1.0.17 | 2 / 27 | |
| 1.0.16 | 2 / 26 | |
| 1.0.15 | 2 / 26 | |
| 1.0.14 | 2 / 26 | |
| 1.0.13 | 2 / 26 | |
| 1.0.12 | 2 / 26 | |
| 1.0.11 | 2 / 26 | |
| 1.0.10 | 2 / 26 | |
| 1.0.9 | 2 / 26 | |
| 1.0.8 | 2 / 26 | |
| 1.0.7 | 2 / 26 | |
| 1.0.6 | 2 / 26 | |
| 1.0.5 | 2 / 26 | |
| 1.0.4 | 2 / 26 | |
| 1.0.3 | 2 / 18 | |
| 1.0.2 | 2 / 18 | |
| 1.0.1 | 2 / 18 | |
| 1.0.0 | 2 / 22 |
v1.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
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.3
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. Only ~12% of npm packages have provenance, so this is common but not ideal.