@bigbinary/neeto-molecules
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/cjs/index.es5.min-CUvhPmKJ.js | AI (source-diff): Standard minified bundle (countries-list data); not obfuscated malicious code. | ai | |
| source-diff | obfuscated-file:dist/index.es5.min-B2AiaKmd.js | AI (source-diff): ESM equivalent of the same minified countries-list bundle; benign. | ai | |
| source-diff | obfuscated-file:dist/cjs/v2/DocumentEditor.js | AI (source-diff): Standard Rollup minified dist output for a React component; readable imports visible in sample. | ai | |
| source-diff | obfuscated-file:dist/v2/DocumentEditor.js | AI (source-diff): Standard Rollup minified dist output for a React component; readable imports visible in sample. | ai |
Versions (showing 100 of 167)
| Version | Deps | Published |
|---|---|---|
| 5.1.18 | 0 / 183 | |
| 5.1.17 | 0 / 183 | |
| 5.1.16 | 0 / 183 | |
| 5.1.15 | 0 / 183 | |
| 5.1.14 | 0 / 183 | |
| 5.1.13 | 0 / 183 | |
| 5.1.12 | 0 / 183 | |
| 5.1.11 | 0 / 183 | |
| 5.1.10 | 0 / 183 | |
| 5.1.9 | 0 / 183 | |
| 5.1.8 | 0 / 183 | |
| 5.1.7 | 0 / 183 | |
| 5.1.6 | 0 / 183 | |
| 5.1.5 | 0 / 183 | |
| 5.1.4 | 0 / 183 | |
| 5.1.3 | 0 / 183 | |
| 5.1.2 | 0 / 183 | |
| 5.1.1 | 0 / 183 | |
| 5.1.0 | 0 / 183 | |
| 5.0.0 | 0 / 183 | |
| 4.3.6 | 0 / 183 | |
| 4.3.5 | 0 / 183 | |
| 4.3.4 | 0 / 183 | |
| 4.3.3 | 0 / 183 | |
| 4.3.2 | 0 / 183 | |
| 4.3.1 | 0 / 183 | |
| 4.3.0 | 0 / 183 | |
| 4.2.0 | 0 / 183 | |
| 4.1.75 | 0 / 183 | |
| 4.1.74 | 0 / 183 | |
| 4.1.73 | 0 / 183 | |
| 4.1.72 | 0 / 183 | |
| 4.1.71 | 0 / 183 | |
| 4.1.70 | 0 / 183 | |
| 4.1.69 | 0 / 183 | |
| 4.1.68 | 0 / 183 | |
| 4.1.67 | 0 / 183 | |
| 4.1.66 | 0 / 183 | |
| 4.1.65 | 0 / 183 | |
| 4.1.64 | 0 / 183 | |
| 4.1.63 | 0 / 183 | |
| 4.1.62 | 0 / 183 | |
| 4.1.61 | 0 / 183 | |
| 4.1.60 | 0 / 182 | |
| 4.1.59 | 0 / 182 | |
| 4.1.58 | 0 / 182 | |
| 4.1.57 | 0 / 182 | |
| 4.1.56 | 0 / 182 | |
| 4.1.55 | 0 / 181 | |
| 4.1.54 | 0 / 181 | |
| 4.1.53 | 0 / 181 | |
| 4.1.52 | 0 / 181 | |
| 4.1.51 | 0 / 181 | |
| 4.1.50 | 0 / 181 | |
| 4.1.49 | 0 / 181 | |
| 4.1.48 | 0 / 181 | |
| 4.1.47 | 0 / 181 | |
| 4.1.46 | 0 / 174 | |
| 4.1.45 | 0 / 174 | |
| 4.1.44 | 0 / 174 | |
| 4.1.43 | 0 / 174 | |
| 4.1.42 | 0 / 174 | |
| 4.1.41 | 0 / 174 | |
| 4.1.40 | 0 / 174 | |
| 4.1.39 | 0 / 174 | |
| 4.1.38 | 0 / 174 | |
| 4.1.37 | 0 / 174 | |
| 4.1.36 | 0 / 174 | |
| 4.1.35 | 0 / 174 | |
| 4.1.34 | 0 / 174 | |
| 4.1.33 | 0 / 173 | |
| 4.1.32 | 0 / 173 | |
| 4.1.31 | 0 / 173 | |
| 4.1.30 | 0 / 173 | |
| 4.1.29 | 0 / 173 | |
| 4.1.28 | 0 / 173 | |
| 4.1.27 | 0 / 173 | |
| 4.1.26 | 0 / 173 | |
| 4.1.25 | 0 / 173 | |
| 4.1.24 | 0 / 173 | |
| 4.1.23 | 0 / 173 | |
| 4.1.22 | 0 / 173 | |
| 4.1.21 | 0 / 173 | |
| 4.1.20 | 0 / 173 | |
| 4.1.19 | 0 / 173 | |
| 4.1.18 | 0 / 173 | |
| 4.1.17 | 0 / 173 | |
| 4.1.16 | 0 / 173 | |
| 4.1.15 | 0 / 173 | |
| 4.1.14 | 0 / 173 | |
| 4.1.13 | 0 / 173 | |
| 4.1.12 | 0 / 173 | |
| 4.1.11 | 0 / 173 | |
| 4.1.10 | 0 / 173 | |
| 4.1.9 | 0 / 173 | |
| 4.1.8 | 0 / 173 | |
| 4.1.7 | 0 / 173 | |
| 4.1.6 | 0 / 173 | |
| 4.1.5 | 0 / 173 | |
| 4.1.4 | 0 / 173 |
v4.1.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.