@e-mc/types
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:eval-usage | AI (semgrep): eval parses a regex-matched object literal for config parsing; not arbitrary external input. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Standard ESM/CJS interop helper (requireESM); stable pattern across this package's versions. | ai |
Versions (showing 100 of 175)
| Version | Deps | Published |
|---|---|---|
| 0.14.5 | 2 / 1 | |
| 0.14.4 | 2 / 1 | |
| 0.14.3 | 2 / 1 | |
| 0.14.2 | 2 / 1 | |
| 0.14.1 | 2 / 1 | |
| 0.14.0 | 2 / 1 | |
| 0.13.11 | 2 / 1 | |
| 0.13.10 | 2 / 1 | |
| 0.13.9 | 2 / 1 | |
| 0.13.8 | 2 / 1 | |
| 0.13.7 | 2 / 1 | |
| 0.13.6 | 2 / 1 | |
| 0.13.5 | 2 / 1 | |
| 0.13.4 | 2 / 1 | |
| 0.13.3 | 2 / 1 | |
| 0.13.2 | 2 / 1 | |
| 0.13.1 | 2 / 1 | |
| 0.13.0 | 2 / 1 | |
| 0.12.17 | 2 / 1 | |
| 0.12.16 | 2 / 1 | |
| 0.12.15 | 2 / 1 | |
| 0.12.14 | 2 / 1 | |
| 0.12.13 | 2 / 1 | |
| 0.12.12 | 2 / 1 | |
| 0.12.11 | 2 / 1 | |
| 0.12.10 | 2 / 1 | |
| 0.12.9 | 2 / 1 | |
| 0.12.8 | 2 / 1 | |
| 0.12.7 | 2 / 1 | |
| 0.12.6 | 2 / 1 | |
| 0.12.5 | 2 / 1 | |
| 0.12.4 | 2 / 1 | |
| 0.12.3 | 2 / 1 | |
| 0.12.2 | 2 / 1 | |
| 0.12.1 | 2 / 1 | |
| 0.12.0 | 2 / 1 | |
| 0.11.18 | 2 / 1 | |
| 0.11.17 | 2 / 1 | |
| 0.11.16 | 2 / 1 | |
| 0.11.15 | 2 / 1 | |
| 0.11.14 | 2 / 1 | |
| 0.11.13 | 2 / 1 | |
| 0.11.12 | 2 / 1 | |
| 0.11.11 | 2 / 1 | |
| 0.11.10 | 2 / 1 | |
| 0.11.9 | 2 / 1 | |
| 0.11.8 | 2 / 1 | |
| 0.11.7 | 2 / 1 | |
| 0.11.5 | 2 / 1 | |
| 0.11.4 | 2 / 1 | |
| 0.11.3 | 2 / 1 | |
| 0.11.2 | 2 / 1 | |
| 0.11.1 | 2 / 1 | |
| 0.11.0 | 1 / 1 | |
| 0.10.21 | 2 / 1 | |
| 0.10.20 | 2 / 1 | |
| 0.10.19 | 2 / 1 | |
| 0.10.18 | 2 / 1 | |
| 0.10.17 | 2 / 1 | |
| 0.10.16 | 2 / 1 | |
| 0.10.15 | 2 / 1 | |
| 0.10.14 | 2 / 1 | |
| 0.10.13 | 2 / 1 | |
| 0.10.12 | 2 / 1 | |
| 0.10.11 | 2 / 1 | |
| 0.10.10 | 2 / 1 | |
| 0.10.9 | 2 / 1 | |
| 0.10.8 | 2 / 1 | |
| 0.10.7 | 2 / 1 | |
| 0.10.6 | 1 / 1 | |
| 0.10.5 | 1 / 1 | |
| 0.10.4 | 1 / 1 | |
| 0.10.3 | 1 / 1 | |
| 0.10.2 | 1 / 1 | |
| 0.10.1 | 1 / 1 | |
| 0.10.0 | 1 / 1 | |
| 0.9.29 | 2 / 1 | |
| 0.9.28 | 2 / 1 | |
| 0.9.27 | 2 / 1 | |
| 0.9.26 | 2 / 1 | |
| 0.9.25 | 2 / 1 | |
| 0.9.24 | 2 / 1 | |
| 0.9.23 | 2 / 1 | |
| 0.9.22 | 2 / 1 | |
| 0.9.21 | 2 / 1 | |
| 0.9.20 | 2 / 1 | |
| 0.9.19 | 2 / 1 | |
| 0.9.18 | 2 / 1 | |
| 0.9.17 | 2 / 1 | |
| 0.9.16 | 2 / 1 | |
| 0.9.15 | 1 / 1 | |
| 0.9.14 | 1 / 1 | |
| 0.9.13 | 1 / 1 | |
| 0.9.12 | 1 / 1 | |
| 0.9.11 | 1 / 1 | |
| 0.9.10 | 1 / 1 | |
| 0.9.9 | 1 / 1 | |
| 0.9.8 | 1 / 1 | |
| 0.9.7 | 1 / 1 | |
| 0.9.6 | 1 / 1 |
v0.14.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.