api-toc
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is the intentional core behavior of this package — it loads JS files from a directory to build an API TOC. Not a security risk in this context. | ai | |
| dependencies | unvetted-dep:code-context | AI (dependencies): code-context is authored by the same publisher (jonschlinkert) and is a legitimate utility for parsing JS code context, directly aligned with this package's purpose. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.3.2 | 5 / 2 | |
| 0.3.1 | 5 / 2 | |
| 0.3.0 | 7 / 3 | |
| 0.2.0 | 4 / 2 | |
| 0.1.2 | 4 / 2 | |
| 0.1.1 | 4 / 2 | |
| 0.1.0 | 4 / 2 |
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.