@aiready/context-analyzer
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:coverage/prettify.js | AI (source-diff): Vendored google-code-prettify lib bundled with Istanbul coverage output, not obfuscated malware. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Coverage/report JSON artifacts accidentally packaged, not injected code. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common; no other risk signals present for this package. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Script only creates dist dir and empty cli.js stub; purely filesystem setup, no network or code execution. | ai |
Versions (showing 49 of 149)
| Version | Deps | Published |
|---|---|---|
| 0.9.8 | 4 / 6 | |
| 0.9.6 | 4 / 6 | |
| 0.9.5 | 4 / 6 | |
| 0.9.4 | 4 / 6 | |
| 0.9.1 | 4 / 6 | |
| 0.9.0 | 4 / 6 | |
| 0.8.3 | 4 / 6 | |
| 0.8.0 | 4 / 6 | |
| 0.7.19 | 4 / 6 | |
| 0.7.18 | 4 / 6 | |
| 0.7.17 | 4 / 6 | |
| 0.7.16 | 4 / 6 | |
| 0.7.15 | 4 / 6 | |
| 0.7.12 | 4 / 6 | |
| 0.7.11 | 4 / 6 | |
| 0.7.7 | 4 / 6 | |
| 0.7.6 | 4 / 6 | |
| 0.7.5 | 4 / 6 | |
| 0.7.4 | 4 / 6 | |
| 0.7.3 | 4 / 6 | |
| 0.7.2 | 4 / 6 | |
| 0.7.1 | 4 / 6 | |
| 0.7.0 | 4 / 6 | |
| 0.6.0 | 4 / 6 | |
| 0.5.3 | 4 / 6 | |
| 0.5.1 | 4 / 6 | |
| 0.5.0 | 4 / 6 | |
| 0.4.6 | 4 / 6 | |
| 0.4.5 | 4 / 6 | |
| 0.4.4 | 4 / 6 | |
| 0.4.3 | 4 / 6 | |
| 0.4.2 | 4 / 6 | |
| 0.4.1 | 4 / 6 | |
| 0.4.0 | 4 / 6 | |
| 0.3.8 | 3 / 5 | |
| 0.3.7 | 3 / 5 | |
| 0.3.6 | 3 / 5 | |
| 0.3.5 | 3 / 5 | |
| 0.3.4 | 3 / 5 | |
| 0.3.3 | 3 / 5 | |
| 0.3.1 | 3 / 5 | |
| 0.3.0 | 3 / 5 | |
| 0.2.1 | 3 / 5 | |
| 0.2.0 | 3 / 5 | |
| 0.1.4 | 3 / 5 | |
| 0.1.3 | 3 / 5 | |
| 0.1.2 | 3 / 5 | |
| 0.1.1 | 3 / 5 | |
| 0.1.0 | 3 / 5 |
v0.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.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.
v0.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.