@drumee/server-essentials
Drumee server essential components
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads a fixed sysEnvFile path (env config JSON), not arbitrary user-controlled input. | ai |
Versions (showing 99 of 99)
| Version | Deps | Published |
|---|---|---|
| 1.3.6 | 13 / 0 | |
| 1.3.5 | 13 / 0 | |
| 1.3.4 | 13 / 0 | |
| 1.3.2 | 13 / 0 | |
| 1.3.1 | 13 / 0 | |
| 1.3.0 | 13 / 0 | |
| 1.2.44 | 13 / 0 | |
| 1.2.43 | 13 / 0 | |
| 1.2.42 | 12 / 0 | |
| 1.2.41 | 12 / 0 | |
| 1.2.40 | 12 / 0 | |
| 1.2.39 | 12 / 0 | |
| 1.2.38 | 12 / 0 | |
| 1.2.37 | 12 / 0 | |
| 1.2.36 | 12 / 0 | |
| 1.2.35 | 12 / 0 | |
| 1.2.34 | 12 / 0 | |
| 1.2.33 | 12 / 0 | |
| 1.2.32 | 12 / 0 | |
| 1.2.31 | 12 / 0 | |
| 1.2.30 | 12 / 0 | |
| 1.2.29 | 12 / 0 | |
| 1.2.28 | 12 / 0 | |
| 1.2.27 | 12 / 0 | |
| 1.2.26 | 12 / 0 | |
| 1.2.25 | 12 / 0 | |
| 1.2.24 | 12 / 0 | |
| 1.2.23 | 12 / 0 | |
| 1.2.22 | 12 / 0 | |
| 1.2.21 | 12 / 0 | |
| 1.2.20 | 12 / 0 | |
| 1.2.19 | 12 / 0 | |
| 1.2.18 | 12 / 0 | |
| 1.2.17 | 12 / 0 | |
| 1.2.15 | 12 / 0 | |
| 1.2.13 | 12 / 0 | |
| 1.2.12 | 12 / 0 | |
| 1.2.11 | 12 / 0 | |
| 1.2.10 | 12 / 0 | |
| 1.2.9 | 12 / 0 | |
| 1.2.8 | 12 / 0 | |
| 1.2.7 | 12 / 0 | |
| 1.2.6 | 12 / 0 | |
| 1.2.5 | 12 / 0 | |
| 1.2.4 | 12 / 0 | |
| 1.2.3 | 12 / 0 | |
| 1.2.2 | 12 / 0 | |
| 1.2.1 | 12 / 0 | |
| 1.1.37 | 12 / 0 | |
| 1.1.36 | 12 / 0 | |
| 1.1.35 | 12 / 0 | |
| 1.1.34 | 12 / 0 | |
| 1.1.33 | 12 / 0 | |
| 1.1.32 | 12 / 0 | |
| 1.1.31 | 12 / 0 | |
| 1.1.29 | 12 / 0 | |
| 1.1.21 | 11 / 0 | |
| 1.1.20 | 11 / 0 | |
| 1.1.19 | 11 / 0 | |
| 1.1.18 | 11 / 0 | |
| 1.1.17 | 11 / 0 | |
| 1.1.16 | 11 / 0 | |
| 1.1.15 | 11 / 0 | |
| 1.1.14 | 11 / 0 | |
| 1.1.13 | 11 / 0 | |
| 1.1.12 | 11 / 0 | |
| 1.1.11 | 11 / 0 | |
| 1.1.10 | 11 / 0 | |
| 1.1.9 | 11 / 0 | |
| 1.1.8 | 11 / 0 | |
| 1.1.7 | 11 / 0 | |
| 1.1.6 | 10 / 0 | |
| 1.1.5 | 10 / 0 | |
| 1.1.4 | 10 / 0 | |
| 1.1.3 | 10 / 0 | |
| 1.1.2 | 10 / 0 | |
| 1.1.1 | 10 / 0 | |
| 1.0.26 | 10 / 0 | |
| 1.0.25 | 10 / 0 | |
| 1.0.24 | 10 / 0 | |
| 1.0.23 | 10 / 0 | |
| 1.0.22 | 10 / 0 | |
| 1.0.21 | 10 / 0 | |
| 1.0.20 | 10 / 0 | |
| 1.0.19 | 10 / 0 | |
| 1.0.18 | 10 / 0 | |
| 1.0.17 | 10 / 0 | |
| 1.0.16 | 10 / 0 | |
| 1.0.15 | 10 / 0 | |
| 1.0.14 | 10 / 0 | |
| 1.0.13 | 10 / 0 | |
| 1.0.12 | 10 / 0 | |
| 1.0.11 | 10 / 0 | |
| 1.0.10 | 10 / 0 | |
| 1.0.9 | 10 / 0 | |
| 1.0.4 | 9 / 0 | |
| 1.0.2 | 9 / 0 | |
| 1.0.1 | 9 / 0 | |
| 1.0.0 | 9 / 0 |
v1.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.