doctoc
Generates TOC for markdown files of local git repo.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): doctoc publishes via GitHub Actions with SLSA provenance attestation from the official thlorenz/doctoc repo. The publisher change reflects CI/CD automation, not a takeover. | ai | |
| provenance | slsa-provenance | AI (provenance): SLSA provenance attestation is a positive signal confirming legitimate CI/CD publishing; no action needed. | ai |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 2.4.1 | 5 / 1 | |
| 2.4.0 | 6 / 1 | |
| 2.3.0 | 6 / 1 | |
| 2.2.1 | 6 / 1 | |
| 2.2.0 | 6 / 1 | |
| 2.1.0 | 6 / 1 | |
| 2.0.1 | 6 / 1 | |
| 2.0.0 | 6 / 1 | |
| 1.4.0 | 6 / 1 | |
| 1.3.1 | 6 / 1 | |
| 1.3.0 | 6 / 1 | |
| 1.2.0 | 6 / 1 | |
| 1.1.1 | 6 / 1 | |
| 1.1.0 | 6 / 1 | |
| 1.0.0 | 6 / 1 | |
| 0.15.0 | 5 / 1 | |
| 0.14.2 | 5 / 1 | |
| 0.14.1 | 5 / 1 | |
| 0.14.0 | 5 / 1 | |
| 0.13.0 | 5 / 1 | |
| 0.12.0 | 5 / 1 | |
| 0.11.0 | 4 / 1 | |
| 0.10.0 | 4 / 1 | |
| 0.9.1 | 4 / 1 | |
| 0.9.0 | 4 / 1 | |
| 0.8.0 | 4 / 1 | |
| 0.7.1 | 4 / 1 | |
| 0.7.0 | 4 / 1 | |
| 0.6.0 | 4 / 1 | |
| 0.5.3 | 3 / 1 | |
| 0.5.2 | 3 / 1 | |
| 0.5.1 | 3 / 1 | |
| 0.4.5 | 2 / 1 | |
| 0.4.4 | 2 / 1 | |
| 0.4.3 | 2 / 1 | |
| 0.4.2 | 2 / 1 | |
| 0.4.1 | 2 / 1 | |
| 0.4.0 | 2 / 1 | |
| 0.3.0 | 2 / 1 | |
| 0.2.1 | 2 / 1 | |
| 0.2.0 | 2 / 1 | |
| 0.1.0 | 1 / 0 | |
| 0.0.3 | 1 / 0 | |
| 0.0.2 | 1 / 0 | |
| 0.0.1 | 1 / 0 |
v2.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.3.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-20. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-09-22. This could indicate a legitimate maintainer transition or an account compromise.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-10-13. This could indicate a legitimate maintainer transition or an account compromise.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.