@bigbinary/neeto-atoms
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
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/DataTable-XA82zdPA.js | AI (source-diff): Standard Rollup bundle output with readable imports; long lines are minified but not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/cjs/DataTable-Cw0ly-hT.js | AI (source-diff): Standard Rollup CJS bundle with sourcemaps; minified lines are normal build output for this UI component library. | ai | |
| source-diff | obfuscated-file:dist/cjs/DataTable-DhWDzUWw.js | AI (source-diff): Standard Rollup CJS bundle output; readable imports and license headers confirm legitimate minification, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/cjs/DataTable-BOeCq0s4.js | AI (source-diff): Standard Rollup CJS bundle with readable imports and source maps; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/cjs/DataTable-BBxgDBnO.js | AI (source-diff): Standard Rollup CJS bundle output; long lines are minified React component code, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/cjs/DataTable-BynOh4Bs.js | AI (source-diff): Standard Rollup minified bundle output; sample confirms legitimate React component code, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/cjs/DataTable-Dg0pX7Ng.js | AI (source-diff): Standard Rollup CJS bundle with readable imports and license headers; long lines are minified but not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/cjs/DataTable-Bc9o5j6-.js | AI (source-diff): Minified Rollup bundle with readable imports and license headers; not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/cjs/DataTable-D_rEai97.js | AI (source-diff): Standard Rollup CJS bundle with readable imports and license headers; long lines are minified but not obfuscated. | ai | |
| phantom-deps | phantom-dep:@fontsource-variable/geist | AI (phantom-deps): Font package referenced in config; stable pattern for component libraries. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal component library; missing metadata (repo, keywords) is expected for monorepo packages. | ai | |
| source-diff | obfuscated-file:dist/cjs/index-CPmGpPzg.js | AI (source-diff): Standard Rollup minified bundle output; sample shows only lucide-react icons and React components, no malicious code. | ai | |
| source-diff | obfuscated-file:dist/index-CDo_esrR.js | AI (source-diff): Standard Rollup ESM minified bundle; sample shows lucide-react icons and CSS injection helper, no malicious code. | ai |
Versions (showing 77 of 77)
| Version | Deps | Published |
|---|---|---|
| 1.0.81 | 0 / 115 | |
| 1.0.80 | 0 / 115 | |
| 1.0.79 | 0 / 115 | |
| 1.0.78 | 0 / 115 | |
| 1.0.77 | 0 / 115 | |
| 1.0.76 | 0 / 115 | |
| 1.0.75 | 0 / 115 | |
| 1.0.74 | 0 / 115 | |
| 1.0.73 | 0 / 115 | |
| 1.0.72 | 0 / 115 | |
| 1.0.71 | 0 / 115 | |
| 1.0.70 | 0 / 115 | |
| 1.0.69 | 0 / 115 | |
| 1.0.68 | 0 / 115 | |
| 1.0.67 | 0 / 115 | |
| 1.0.66 | 0 / 115 | |
| 1.0.65 | 0 / 115 | |
| 1.0.64 | 0 / 115 | |
| 1.0.63 | 0 / 115 | |
| 1.0.62 | 0 / 115 | |
| 1.0.61 | 0 / 115 | |
| 1.0.60 | 0 / 115 | |
| 1.0.59 | 0 / 115 | |
| 1.0.58 | 0 / 115 | |
| 1.0.57 | 0 / 115 | |
| 1.0.56 | 0 / 115 | |
| 1.0.55 | 0 / 115 | |
| 1.0.54 | 0 / 115 | |
| 1.0.53 | 0 / 115 | |
| 1.0.52 | 0 / 115 | |
| 1.0.51 | 0 / 115 | |
| 1.0.50 | 0 / 115 | |
| 1.0.49 | 0 / 115 | |
| 1.0.48 | 0 / 115 | |
| 1.0.47 | 0 / 115 | |
| 1.0.46 | 0 / 115 | |
| 1.0.45 | 0 / 115 | |
| 1.0.44 | 0 / 115 | |
| 1.0.43 | 0 / 115 | |
| 1.0.42 | 0 / 115 | |
| 1.0.41 | 0 / 115 | |
| 1.0.40 | 0 / 115 | |
| 1.0.39 | 0 / 115 | |
| 1.0.38 | 0 / 115 | |
| 1.0.37 | 0 / 115 | |
| 1.0.36 | 0 / 113 | |
| 1.0.35 | 0 / 113 | |
| 1.0.34 | 0 / 113 | |
| 1.0.33 | 0 / 113 | |
| 1.0.32 | 0 / 113 | |
| 1.0.31 | 0 / 113 | |
| 1.0.30 | 0 / 113 | |
| 1.0.29 | 0 / 113 | |
| 1.0.28 | 0 / 113 | |
| 1.0.27 | 0 / 113 | |
| 1.0.26 | 0 / 113 | |
| 1.0.25 | 0 / 113 | |
| 1.0.24 | 0 / 113 | |
| 1.0.23 | 0 / 113 | |
| 1.0.22 | 0 / 113 | |
| 1.0.21 | 0 / 113 | |
| 1.0.20 | 0 / 113 | |
| 1.0.19 | 0 / 113 | |
| 1.0.18 | 0 / 113 | |
| 1.0.17 | 0 / 113 | |
| 1.0.16 | 0 / 113 | |
| 1.0.15 | 0 / 112 | |
| 1.0.14 | 0 / 112 | |
| 1.0.13 | 0 / 112 | |
| 1.0.12 | 0 / 112 | |
| 1.0.11 | 2 / 110 | |
| 1.0.10 | 2 / 108 | |
| 1.0.9 | 0 / 105 | |
| 1.0.8 | 74 / 29 | |
| 1.0.7 | 73 / 29 | |
| 1.0.6 | 73 / 29 | |
| 1.0.5 | 0 / 100 |
v1.0.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.53
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.36
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.35
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.34
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.33
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.32
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.31
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.30
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.29
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.28
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.27
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.24
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package 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. Consider requesting the maintainer enable provenance via CI/CD.
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. 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.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.