@neurcode-ai/contracts
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): No content change vs prior version; likely CI metadata gap, not a takeover. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Benign rapid patch release from a trusted publisher with clean history. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 0.2.25 | 0 / 3 | |
| 0.2.24 | 0 / 3 | |
| 0.2.23 | 0 / 3 | |
| 0.2.22 | 0 / 3 | |
| 0.2.21 | 0 / 3 | |
| 0.2.20 | 0 / 3 | |
| 0.2.19 | 0 / 3 | |
| 0.2.18 | 0 / 3 | |
| 0.2.17 | 0 / 3 | |
| 0.2.16 | 0 / 3 | |
| 0.2.15 | 0 / 3 | |
| 0.2.14 | 0 / 3 | |
| 0.2.13 | 0 / 3 | |
| 0.2.12 | 0 / 3 | |
| 0.2.11 | 0 / 3 | |
| 0.2.10 | 0 / 3 | |
| 0.2.9 | 0 / 3 | |
| 0.2.8 | 0 / 3 | |
| 0.2.7 | 0 / 3 | |
| 0.2.6 | 0 / 3 | |
| 0.2.5 | 0 / 3 | |
| 0.2.4 | 0 / 3 | |
| 0.2.3 | 0 / 3 | |
| 0.2.2 | 0 / 3 | |
| 0.2.1 | 0 / 3 | |
| 0.2.0 | 0 / 3 | |
| 0.1.3 | 0 / 3 | |
| 0.1.2 | 0 / 3 | |
| 0.1.1 | 0 / 3 | |
| 0.1.0 | 0 / 3 |
v0.2.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.19
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: neurcode.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.18
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: neurcode.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.17
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: neurcode.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.16
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: neurcode.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.15
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: neurcode.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: neurcode.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: neurcode.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: neurcode.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.