@plugjs/plug
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 |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): Build tool fork runner intentionally propagates process.env to child processes; stable pattern for this package. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped build framework @plugjs/plug; no resemblance to pg (postgres client) in purpose or namespace. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node is a type-only dep used at compile time; not imported at runtime by convention. | ai |
Versions (showing 100 of 123)
| Version | Deps | Published |
|---|---|---|
| 0.6.116 | 5 / 1 | |
| 0.6.115 | 5 / 1 | |
| 0.6.114 | 5 / 1 | |
| 0.6.113 | 5 / 1 | |
| 0.6.112 | 5 / 1 | |
| 0.6.111 | 5 / 1 | |
| 0.6.110 | 5 / 1 | |
| 0.6.109 | 5 / 1 | |
| 0.6.108 | 5 / 1 | |
| 0.6.107 | 5 / 1 | |
| 0.6.106 | 5 / 1 | |
| 0.6.105 | 5 / 1 | |
| 0.6.104 | 5 / 1 | |
| 0.6.103 | 5 / 1 | |
| 0.6.102 | 5 / 1 | |
| 0.6.101 | 5 / 1 | |
| 0.6.100 | 5 / 1 | |
| 0.6.99 | 5 / 1 | |
| 0.6.98 | 5 / 1 | |
| 0.6.97 | 5 / 1 | |
| 0.6.96 | 5 / 1 | |
| 0.6.95 | 5 / 1 | |
| 0.6.94 | 5 / 1 | |
| 0.6.93 | 5 / 1 | |
| 0.6.92 | 5 / 1 | |
| 0.6.91 | 5 / 1 | |
| 0.6.90 | 5 / 1 | |
| 0.6.89 | 5 / 1 | |
| 0.6.88 | 5 / 1 | |
| 0.6.87 | 5 / 1 | |
| 0.6.86 | 5 / 1 | |
| 0.6.85 | 5 / 1 | |
| 0.6.84 | 5 / 1 | |
| 0.6.83 | 5 / 1 | |
| 0.6.82 | 5 / 1 | |
| 0.6.81 | 5 / 1 | |
| 0.6.80 | 5 / 1 | |
| 0.6.79 | 5 / 1 | |
| 0.6.78 | 5 / 1 | |
| 0.6.77 | 5 / 1 | |
| 0.6.76 | 5 / 1 | |
| 0.6.75 | 5 / 1 | |
| 0.6.74 | 5 / 1 | |
| 0.6.73 | 5 / 1 | |
| 0.6.72 | 5 / 1 | |
| 0.6.71 | 5 / 1 | |
| 0.6.70 | 5 / 1 | |
| 0.6.69 | 5 / 1 | |
| 0.6.68 | 5 / 1 | |
| 0.6.67 | 5 / 1 | |
| 0.6.66 | 5 / 1 | |
| 0.6.65 | 5 / 1 | |
| 0.6.64 | 5 / 1 | |
| 0.6.63 | 5 / 1 | |
| 0.6.62 | 5 / 1 | |
| 0.6.61 | 5 / 1 | |
| 0.6.60 | 5 / 1 | |
| 0.6.59 | 5 / 1 | |
| 0.6.58 | 5 / 1 | |
| 0.6.57 | 5 / 1 | |
| 0.6.56 | 5 / 1 | |
| 0.6.55 | 5 / 1 | |
| 0.6.54 | 5 / 1 | |
| 0.6.53 | 5 / 1 | |
| 0.6.52 | 5 / 1 | |
| 0.6.51 | 5 / 1 | |
| 0.6.50 | 5 / 1 | |
| 0.6.49 | 5 / 1 | |
| 0.6.48 | 5 / 1 | |
| 0.6.47 | 5 / 1 | |
| 0.6.46 | 5 / 1 | |
| 0.6.45 | 5 / 1 | |
| 0.6.44 | 5 / 1 | |
| 0.6.43 | 5 / 1 | |
| 0.6.41 | 5 / 1 | |
| 0.6.40 | 5 / 1 | |
| 0.6.39 | 5 / 1 | |
| 0.6.38 | 5 / 1 | |
| 0.6.37 | 5 / 1 | |
| 0.6.36 | 5 / 1 | |
| 0.6.35 | 5 / 1 | |
| 0.6.34 | 5 / 1 | |
| 0.6.33 | 5 / 1 | |
| 0.6.32 | 5 / 1 | |
| 0.6.31 | 5 / 1 | |
| 0.6.30 | 5 / 1 | |
| 0.6.29 | 5 / 1 | |
| 0.6.28 | 5 / 1 | |
| 0.6.27 | 5 / 1 | |
| 0.6.26 | 5 / 1 | |
| 0.6.25 | 5 / 1 | |
| 0.6.24 | 5 / 1 | |
| 0.6.23 | 5 / 1 | |
| 0.6.22 | 5 / 1 | |
| 0.6.21 | 5 / 1 | |
| 0.6.20 | 5 / 1 | |
| 0.6.19 | 5 / 1 | |
| 0.6.18 | 5 / 1 | |
| 0.6.17 | 5 / 1 | |
| 0.6.16 | 5 / 1 |
v0.6.116
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.115
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.114
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.113
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.