@adhdev/mcp-server
ADHDev MCP server — expose IDE agents as MCP tools
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 | missing-githead | AI (provenance): Publisher has clean 114/0 track record; no attestation regression, just missing gitHead metadata. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is the publisher's own first-party monorepo sibling package. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 1.0.25 | 2 / 4 | |
| 1.0.24 | 2 / 4 | |
| 1.0.23 | 2 / 4 | |
| 1.0.22 | 2 / 4 | |
| 1.0.20 | 2 / 4 | |
| 1.0.19 | 2 / 4 | |
| 1.0.18 | 2 / 4 | |
| 1.0.17 | 2 / 4 | |
| 1.0.16 | 2 / 4 | |
| 1.0.15 | 2 / 4 | |
| 1.0.14 | 2 / 4 | |
| 1.0.13 | 2 / 4 | |
| 1.0.12 | 2 / 4 | |
| 1.0.10 | 2 / 4 | |
| 1.0.9 | 2 / 4 | |
| 1.0.8 | 2 / 4 | |
| 1.0.7 | 2 / 4 | |
| 1.0.6 | 2 / 4 | |
| 1.0.5 | 2 / 4 | |
| 1.0.4 | 2 / 4 | |
| 1.0.3 | 2 / 4 | |
| 1.0.2 | 2 / 4 | |
| 1.0.1 | 2 / 4 | |
| 1.0.0 | 2 / 4 | |
| 0.9.81 | 1 / 4 | |
| 0.9.80 | 1 / 4 | |
| 0.9.79 | 1 / 4 | |
| 0.9.78 | 1 / 4 | |
| 0.9.77 | 1 / 4 | |
| 0.9.76 | 1 / 4 | |
| 0.9.75 | 1 / 4 | |
| 0.9.74 | 1 / 4 | |
| 0.9.73 | 1 / 4 | |
| 0.9.72 | 1 / 4 | |
| 0.9.71 | 1 / 4 | |
| 0.9.70 | 1 / 4 | |
| 0.9.69 | 1 / 4 | |
| 0.9.68 | 1 / 4 | |
| 0.9.67 | 1 / 4 | |
| 0.9.66 | 1 / 4 | |
| 0.9.65 | 1 / 4 | |
| 0.9.64 | 1 / 4 | |
| 0.9.63 | 1 / 4 | |
| 0.9.62 | 1 / 4 | |
| 0.9.61 | 1 / 4 | |
| 0.9.60 | 1 / 4 | |
| 0.9.59 | 1 / 4 |
v1.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vilmire.
v1.0.0
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: vilmire.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.