@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, so a manually published version cannot be tied back to a reviewed commit.
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 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 2.5.5 | 8 / 8 | |
| 2.5.4 | 8 / 8 | |
| 2.5.3 | 8 / 8 | |
| 2.5.1 | 8 / 8 | |
| 2.5.0 | 8 / 8 | |
| 2.4.5 | 8 / 8 | |
| 2.4.4 | 8 / 8 | |
| 2.4.3 | 8 / 8 | |
| 2.4.2 | 8 / 8 | |
| 2.4.1 | 8 / 8 | |
| 2.3.1 | 8 / 8 | |
| 2.3.0 | 8 / 8 | |
| 2.2.0 | 8 / 8 | |
| 2.1.4 | 8 / 8 | |
| 2.1.0 | 8 / 8 | |
| 2.0.20 | 8 / 8 | |
| 2.0.19 | 8 / 8 | |
| 2.0.18 | 8 / 8 | |
| 2.0.17 | 8 / 8 | |
| 2.0.16 | 8 / 8 | |
| 2.0.15 | 8 / 8 | |
| 2.0.14 | 8 / 8 | |
| 2.0.13 | 8 / 8 | |
| 2.0.12 | 8 / 8 | |
| 2.0.11 | 8 / 8 |
v2.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.