@bigbinary/neeto-integrations-frontend
UI for integrations in neeto products
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/v2/Finish.js | AI (source-diff): CJS counterpart of the same Rollup bundle; same rationale applies. | ai | |
| source-diff | obfuscated-file:dist/v2/Finish.js | AI (source-diff): Standard Rollup bundle output for a React component; long lines are base64-encoded SVG assets, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/success-C6rQdhhF.js | AI (source-diff): Rollup-bundled SVG React component with base64 PNG; long lines are image data, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/success-CsNvTPBG.js | AI (source-diff): CJS variant of the same SVG component; same benign pattern. | ai | |
| dependencies | unvetted-dep:react-router-nav-prompt | AI (dependencies): react-router-nav-prompt is a small, stable navigation-prompt utility; no advisories and pinned to 0.4.1. | ai | |
| provenance | no-provenance | AI (provenance): BigBinary neeto packages consistently lack provenance attestation; stable false positive for this publisher. | ai | |
| phantom-deps | phantom-dep:react-router-nav-prompt | AI (phantom-deps): Used in config/routing setup, not directly imported; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-syntax-dynamic-import | AI (phantom-deps): Framework-scoped Babel plugin loaded by convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:babel-plugin-transform-imports | AI (phantom-deps): Babel plugin referenced in build config, not directly imported; expected pattern. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 4.0.40 | 3 / 120 | |
| 4.0.39 | 3 / 120 | |
| 4.0.38 | 3 / 120 | |
| 4.0.37 | 3 / 120 | |
| 4.0.36 | 3 / 120 | |
| 4.0.35 | 3 / 120 | |
| 4.0.34 | 3 / 120 | |
| 4.0.33 | 3 / 120 | |
| 4.0.32 | 3 / 120 | |
| 4.0.31 | 3 / 120 | |
| 4.0.30 | 3 / 120 | |
| 4.0.29 | 3 / 120 | |
| 4.0.28 | 3 / 120 | |
| 4.0.27 | 3 / 120 | |
| 4.0.26 | 3 / 120 | |
| 4.0.25 | 3 / 120 | |
| 4.0.24 | 3 / 118 | |
| 4.0.23 | 3 / 118 | |
| 4.0.22 | 3 / 118 | |
| 4.0.21 | 3 / 118 | |
| 4.0.20 | 3 / 119 | |
| 4.0.19 | 3 / 119 | |
| 4.0.18 | 3 / 119 | |
| 4.0.17 | 3 / 119 | |
| 4.0.16 | 3 / 119 | |
| 4.0.15 | 3 / 119 | |
| 4.0.14 | 3 / 119 | |
| 4.0.13 | 3 / 119 | |
| 4.0.12 | 3 / 119 | |
| 4.0.11 | 3 / 118 | |
| 4.0.10 | 3 / 117 | |
| 4.0.9 | 3 / 117 | |
| 4.0.8 | 3 / 117 | |
| 4.0.7 | 3 / 117 | |
| 4.0.6 | 3 / 117 | |
| 4.0.5 | 3 / 116 |
v4.0.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.32
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.31
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.30
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.28
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.27
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.26
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.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.