← Home

@podlite/toc

npm Repository Homepage

Auto-generate table of contents from Podlite documents

18
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

zaggaz

Keywords

podlitetoctable-of-contentsmarkdownmarkup-languageheadingnavigationoutlineauto-generatesidebar

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:koa AI (typosquat): Scoped @podlite package in established monorepo; Levenshtein match is noise. ai
typosquat typosquat.levenshtein:got AI (typosquat): Scoped @podlite package in established monorepo; Levenshtein match is noise. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped @podlite package in established monorepo; Levenshtein match is noise. ai
typosquat typosquat.levenshtein:zod AI (typosquat): Scoped @podlite package in established monorepo; Levenshtein match is noise. ai
phantom-deps phantom-dep:react AI (phantom-deps): Declared as both peer and runtime dep; phantom-dep heuristic misfires here. ai
phantom-deps phantom-dep:react-is AI (phantom-deps): Runtime dependency for React ecosystem; phantom-dep heuristic misfires here. ai
phantom-deps phantom-dep:react-dom AI (phantom-deps): Declared as both peer and runtime dep; phantom-dep heuristic misfires here. ai

Versions (showing 18 of 18)

Version Deps Published
0.0.38 4 / 0
0.0.37 4 / 0
0.0.36 4 / 0
0.0.35 4 / 0
0.0.34 4 / 0
0.0.33 4 / 0
0.0.32 4 / 0
0.0.31 4 / 0
0.0.30 4 / 0
0.0.29 4 / 0
0.0.28 4 / 0
0.0.27 4 / 0
0.0.26 4 / 0
0.0.25 4 / 0
0.0.24 4 / 0
0.0.23 4 / 0
0.0.22 4 / 0
0.0.21 4 / 0

v0.0.38

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.37

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.36

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.35

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.34

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.33

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.32

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.29

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.28

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.27

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.26

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.25

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.24

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.23

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.22

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.21

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.