@saltcorn/copilot
AI assistant for building Saltcorn applications
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:markdown-it | AI (dependencies): markdown-it is a well-known, widely-used Markdown renderer; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@saltcorn/data | AI (dependencies): Core Saltcorn data library; expected dependency for all Saltcorn plugins. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate Saltcorn plugin; sparse README/keywords are a style choice, not spam. | ai | |
| provenance | no-provenance | AI (provenance): Saltcorn org does not use Sigstore provenance; consistent across all versions. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 0.8.8 | 7 / 1 | |
| 0.8.7 | 7 / 1 | |
| 0.8.6 | 7 / 1 | |
| 0.8.5 | 7 / 1 | |
| 0.8.4 | 7 / 1 | |
| 0.8.3 | 7 / 1 | |
| 0.8.2 | 7 / 1 | |
| 0.8.1 | 7 / 1 | |
| 0.8.0 | 7 / 1 | |
| 0.5.3 | 6 / 0 | |
| 0.5.1 | 6 / 0 | |
| 0.5.0 | 6 / 0 | |
| 0.4.5 | 4 / 0 | |
| 0.4.4 | 4 / 0 | |
| 0.4.3 | 4 / 0 | |
| 0.4.2 | 4 / 0 | |
| 0.4.1 | 4 / 0 | |
| 0.4.0 | 4 / 0 | |
| 0.3.2 | 4 / 0 | |
| 0.3.1 | 4 / 0 | |
| 0.3.0 | 4 / 0 | |
| 0.2.0 | 4 / 0 | |
| 0.1.1 | 4 / 0 | |
| 0.1.0 | 4 / 0 |
v0.8.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.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.