@bigbinary/neeto-filters-frontend
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/index-BzkSk3Jh.js | AI (source-diff): Standard Rollup-minified CSS+JS bundle output; BigBinary UI component library pattern, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index-DX0qF4mf.js | AI (source-diff): Standard Rollup-minified CSS+JS bundle output; BigBinary UI component library pattern, not obfuscation. | ai | |
| phantom-deps | phantom-dep:react-router-nav-prompt | AI (phantom-deps): Listed as runtime dep; phantom-dep heuristic fires because it's referenced in config, not directly imported in source. | ai | |
| phantom-deps | phantom-dep:babel-plugin-transform-imports | AI (phantom-deps): Babel plugin used via config files, not directly imported — stable false positive for this package. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 4.3.39 | 2 / 121 | |
| 4.3.38 | 2 / 121 | |
| 4.3.37 | 2 / 121 | |
| 4.3.36 | 2 / 121 | |
| 4.3.35 | 2 / 121 | |
| 4.3.34 | 2 / 121 | |
| 4.3.33 | 2 / 121 | |
| 4.3.32 | 2 / 120 | |
| 4.3.31 | 2 / 120 | |
| 4.3.30 | 2 / 121 | |
| 4.3.29 | 2 / 121 | |
| 4.3.28 | 2 / 121 | |
| 4.3.27 | 2 / 121 | |
| 4.3.26 | 2 / 121 | |
| 4.3.25 | 2 / 121 | |
| 4.3.24 | 2 / 119 | |
| 4.3.23 | 2 / 119 | |
| 4.3.22 | 2 / 119 | |
| 4.3.21 | 2 / 119 | |
| 4.3.20 | 2 / 119 | |
| 4.3.19 | 2 / 118 |
v4.3.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.33
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.
v4.3.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.