@bigbinary/neeto-rules-frontend
A repo acts as the source of truth for the new nano's structure, configs, data etc.
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Metadata-only signal, no behavior change; consistent with trusted publisher history. | ai | |
| license | uncommon-license:UNLICENSED | AI (license): Internal proprietary package, expected license choice. | ai | |
| source-diff | obfuscated-file:dist/keyboardShortcuts-NxcrOxzv.js | AI (source-diff): CJS twin of the same minified bundle; benign build artifact. | ai | |
| source-diff | obfuscated-file:dist/keyboardShortcuts-BvIE6AHg.js | AI (source-diff): Minified rollup/CSS-injection bundle, not true obfuscation; consistent with build output. | ai | |
| source-diff | obfuscated-file:dist/keyboardShortcuts-DcvmDX_K.js | AI (source-diff): Bundled rollup output, not true obfuscation; matches package's build pattern. | ai | |
| source-diff | obfuscated-file:dist/keyboardShortcuts-Dg7lUOmj.js | AI (source-diff): Bundled rollup output, not true obfuscation; matches package's build pattern. | ai | |
| phantom-deps | phantom-dep:babel-plugin-transform-imports | AI (phantom-deps): Babel config reference; stable false positive for this build tooling package. | ai | |
| phantom-deps | phantom-dep:react-router-nav-prompt | AI (phantom-deps): Config-only reference, not a security concern 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 |
Versions (showing 91 of 91)
| Version | Deps | Published |
|---|---|---|
| 2.7.10 | 3 / 124 | |
| 2.7.9 | 3 / 124 | |
| 2.7.8 | 3 / 124 | |
| 2.7.7 | 3 / 124 | |
| 2.7.6 | 3 / 124 | |
| 2.7.5 | 3 / 124 | |
| 2.7.4 | 3 / 124 | |
| 2.7.3 | 3 / 124 | |
| 2.7.2 | 3 / 124 | |
| 2.7.1 | 3 / 124 | |
| 2.7.0 | 3 / 124 | |
| 2.6.3 | 3 / 124 | |
| 2.6.2 | 3 / 124 | |
| 2.6.1 | 3 / 124 | |
| 2.6.0 | 3 / 124 | |
| 2.5.65 | 3 / 124 | |
| 2.5.64 | 3 / 124 | |
| 2.5.63 | 3 / 124 | |
| 2.5.62 | 3 / 124 | |
| 2.5.61 | 3 / 124 | |
| 2.5.60 | 3 / 124 | |
| 2.5.59 | 3 / 124 | |
| 2.5.58 | 3 / 123 | |
| 2.5.57 | 3 / 123 | |
| 2.5.56 | 3 / 122 | |
| 2.5.55 | 3 / 122 | |
| 2.5.54 | 3 / 122 | |
| 2.5.53 | 3 / 122 | |
| 2.5.52 | 3 / 123 | |
| 2.5.51 | 3 / 123 | |
| 2.5.50 | 3 / 123 | |
| 2.5.49 | 3 / 124 | |
| 2.5.48 | 3 / 124 | |
| 2.5.46 | 3 / 124 | |
| 2.5.45 | 3 / 124 | |
| 2.5.44 | 3 / 124 | |
| 2.5.43 | 3 / 124 | |
| 2.5.42 | 3 / 124 | |
| 2.5.41 | 3 / 124 | |
| 2.5.40 | 3 / 124 | |
| 2.5.39 | 3 / 124 | |
| 2.5.38 | 3 / 124 | |
| 2.5.37 | 3 / 124 | |
| 2.5.36 | 3 / 124 | |
| 2.5.35 | 3 / 124 | |
| 2.5.34 | 3 / 123 | |
| 2.5.33 | 3 / 123 | |
| 2.5.32 | 3 / 123 | |
| 2.5.31 | 3 / 123 | |
| 2.5.30 | 3 / 123 | |
| 2.5.29 | 3 / 123 | |
| 2.5.28 | 3 / 123 | |
| 2.5.27 | 3 / 122 | |
| 2.5.26 | 3 / 122 | |
| 2.5.25 | 3 / 122 | |
| 2.5.24 | 3 / 122 | |
| 2.5.23 | 3 / 122 | |
| 2.5.22 | 3 / 122 | |
| 2.5.21 | 3 / 122 | |
| 2.5.20 | 3 / 122 | |
| 2.5.19 | 3 / 122 | |
| 2.5.18 | 3 / 122 | |
| 2.5.17 | 3 / 122 | |
| 2.5.16 | 3 / 120 | |
| 2.5.15 | 3 / 119 | |
| 2.5.14 | 3 / 119 | |
| 2.5.13 | 3 / 119 | |
| 2.5.12 | 3 / 119 | |
| 2.5.11 | 3 / 119 | |
| 2.5.10 | 3 / 119 | |
| 2.5.9 | 3 / 119 | |
| 2.5.8 | 3 / 119 | |
| 2.5.7 | 3 / 119 | |
| 2.5.4 | 2 / 118 | |
| 2.5.3 | 2 / 118 | |
| 2.5.2 | 2 / 117 | |
| 2.5.1 | 2 / 117 | |
| 2.5.0 | 2 / 117 | |
| 2.4.2 | 2 / 117 | |
| 2.4.1 | 2 / 117 | |
| 2.4.0 | 2 / 117 | |
| 2.3.1 | 5 / 114 | |
| 2.3.0 | 5 / 114 | |
| 2.2.0 | 5 / 114 | |
| 2.1.0 | 5 / 114 | |
| 2.0.5 | 5 / 114 | |
| 2.0.4 | 5 / 114 | |
| 2.0.3 | 5 / 113 | |
| 2.0.2 | 5 / 113 | |
| 2.0.1 | 5 / 113 | |
| 2.0.0 | 5 / 113 |
v2.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.8
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.
v2.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.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.
v2.7.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.
v2.7.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.
v2.7.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.
v2.7.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.
v2.7.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.
v2.7.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.
v2.6.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.
v2.6.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.
v2.6.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.
v2.6.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.
v2.5.15
2 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.14
2 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.13
2 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.12
2 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.