@heejun/spa-seo-gateway-multi-tenant
Multi-tenant SaaS layer scaffold for spa-seo-gateway (option B)
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
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.9.1 | 3 / 1 | |
| 1.9.0 | 3 / 1 | |
| 1.8.0 | 3 / 1 | |
| 1.7.0 | 3 / 1 | |
| 1.6.0 | 3 / 1 | |
| 1.5.0 | 3 / 1 | |
| 1.4.0 | 3 / 1 | |
| 1.3.0 | 3 / 1 | |
| 1.2.0 | 3 / 1 | |
| 1.1.0 | 3 / 1 | |
| 1.0.0 | 3 / 1 |
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.