@bigbinary/neeto-audit-frontend
Audits neeto frontend codebase for issues and suggests a fix.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Internal bigbinary tooling package; provenance attestation not expected for this org's packages. | ai | |
| license | uncommon-license:UNLICENSED | AI (license): Intentionally proprietary internal package; UNLICENSED is expected and stable across versions. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.4.5 | 8 / 8 | |
| 2.4.4 | 8 / 8 | |
| 2.4.3 | 8 / 8 | |
| 2.4.1 | 8 / 8 | |
| 2.3.1 | 8 / 8 |
v2.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.