@bigbinary/neeto-tags-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): Consistent internal monorepo publish process across 156 versions from trusted publisher. | ai | |
| source-diff | obfuscated-file:dist/cjs/NeetoTags.js | AI (source-diff): Rollup-bundled output with plain requires; long line is bundling, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/NeetoTags.js | AI (source-diff): Rollup-bundled ESM output with plain imports; not obfuscated. | ai | |
| source-diff | obfuscated-file:dist/index-hfjlurOH.js | AI (source-diff): Standard Rollup minified CJS bundle with readable imports; source maps present. Normal build output for this package. | ai | |
| source-diff | obfuscated-file:dist/index-_sNMrsD3.js | AI (source-diff): Standard Rollup minified ESM bundle with readable imports; source maps present. Normal build output for this package. | ai | |
| phantom-deps | phantom-dep:react-router-nav-prompt | AI (phantom-deps): Listed as runtime dep, phantom-dep fires because it's config-referenced; stable false positive 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 loaded via config convention, not direct import; stable false positive. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 2.2.30 | 3 / 119 | |
| 2.2.29 | 3 / 119 | |
| 2.2.28 | 3 / 119 | |
| 2.2.27 | 3 / 119 | |
| 2.2.26 | 3 / 119 | |
| 2.2.25 | 3 / 119 | |
| 2.2.24 | 3 / 119 | |
| 2.2.23 | 3 / 119 | |
| 2.2.22 | 3 / 119 | |
| 2.2.21 | 3 / 119 | |
| 2.2.20 | 3 / 119 | |
| 2.2.19 | 3 / 118 | |
| 2.2.18 | 3 / 118 | |
| 2.2.17 | 3 / 118 | |
| 2.2.16 | 3 / 119 | |
| 2.2.15 | 3 / 119 | |
| 2.2.14 | 3 / 119 | |
| 2.2.13 | 3 / 119 | |
| 2.2.12 | 3 / 119 | |
| 2.2.11 | 3 / 119 | |
| 2.2.10 | 3 / 119 | |
| 2.2.9 | 4 / 118 | |
| 2.2.8 | 3 / 118 | |
| 2.2.7 | 3 / 117 | |
| 2.2.6 | 3 / 117 | |
| 2.2.5 | 3 / 117 | |
| 2.2.4 | 3 / 117 | |
| 2.2.3 | 3 / 117 | |
| 2.2.1 | 3 / 117 | |
| 2.2.0 | 3 / 117 | |
| 2.1.10 | 3 / 116 | |
| 2.1.9 | 3 / 116 | |
| 2.1.8 | 3 / 116 | |
| 2.1.7 | 3 / 116 | |
| 2.1.6 | 3 / 116 | |
| 2.1.4 | 2 / 115 | |
| 2.1.3 | 2 / 114 | |
| 2.1.2 | 4 / 113 | |
| 2.1.1 | 4 / 113 | |
| 2.1.0 | 4 / 113 | |
| 2.0.3 | 4 / 113 | |
| 2.0.2 | 4 / 113 | |
| 2.0.1 | 4 / 113 | |
| 2.0.0 | 4 / 113 |
v2.2.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.10
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.
v2.1.9
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.
v2.1.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.1.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.
v2.1.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.1.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.1.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.1.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.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.
v2.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.
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.