@djangocfg/seo
SEO analytics and indexing diagnostics module with Google Search Console integration and AI-ready reports
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:linkinator | AI (dependencies): linkinator is a well-known link-checking library; appropriate for an SEO/crawler package. | ai | |
| dependencies | unvetted-dep:@googleapis/searchconsole | AI (dependencies): Official Google APIs client for Search Console; directly aligned with package purpose. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): CLI tool dependency; declared but may be used indirectly or in config — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:picocolors | AI (phantom-deps): Terminal styling dep; declared but may be used indirectly — stable false positive for this package. | ai |
Versions (showing 20 of 320)
| Version | Deps | Published |
|---|---|---|
| 2.1.71 | 11 / 6 | |
| 2.1.70 | 11 / 6 | |
| 2.1.69 | 11 / 6 | |
| 2.1.68 | 11 / 6 | |
| 2.1.67 | 11 / 6 | |
| 2.1.66 | 11 / 6 | |
| 2.1.65 | 11 / 6 | |
| 2.1.64 | 11 / 6 | |
| 2.1.63 | 11 / 6 | |
| 2.1.62 | 11 / 6 | |
| 2.1.59 | 11 / 6 | |
| 2.1.58 | 11 / 6 | |
| 2.1.57 | 11 / 6 | |
| 2.1.56 | 11 / 6 | |
| 2.1.55 | 11 / 6 | |
| 2.1.54 | 11 / 6 | |
| 2.1.53 | 11 / 6 | |
| 2.1.52 | 11 / 6 | |
| 2.1.51 | 11 / 6 | |
| 2.1.50 | 11 / 6 |
v2.1.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.