@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, 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/Filters.js | AI (source-diff): Bundled ESM build output, readable imports, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/cjs/Filters.js | AI (source-diff): Bundled rollup/babel output with sourcemaps, not obfuscation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Routine internal team maintainer rotation at established publisher. | 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 | |
| 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 | |
| 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 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 4.3.42 | 2 / 121 | |
| 4.3.41 | 2 / 121 | |
| 4.3.40 | 2 / 121 | |
| 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 | |
| 4.3.15 | 2 / 118 | |
| 4.3.14 | 2 / 118 | |
| 4.3.13 | 2 / 118 | |
| 4.3.12 | 2 / 118 | |
| 4.3.11 | 2 / 118 | |
| 4.3.10 | 2 / 117 | |
| 4.3.7 | 2 / 116 | |
| 4.3.6 | 2 / 115 | |
| 4.3.5 | 2 / 115 | |
| 4.3.4 | 4 / 114 | |
| 4.3.3 | 4 / 114 | |
| 4.3.2 | 4 / 114 | |
| 4.3.1 | 4 / 114 | |
| 4.3.0 | 4 / 114 | |
| 4.2.1 | 4 / 114 | |
| 4.2.0 | 4 / 114 | |
| 4.1.1 | 4 / 114 | |
| 4.1.0 | 4 / 114 | |
| 4.0.1 | 4 / 114 | |
| 4.0.0 | 4 / 113 |
v4.3.15
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: neetohq.
Newly 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.14
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.13
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.12
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.11
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.10
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.7
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.6
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.5
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.4
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.3
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.2
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.1
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.0
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.2.1
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.2.0
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.1.1
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.1.0
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.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.