@claspo/templates
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@claspo/renderer | AI (phantom-deps): Same-org transitive dependency; stable pattern for monorepo packages. | ai | |
| phantom-deps | phantom-dep:@claspo/components | AI (phantom-deps): Same-org transitive dependency; stable pattern for monorepo packages. | ai | |
| phantom-deps | phantom-dep:@claspo/document-connector | AI (phantom-deps): Same-org transitive dependency; stable pattern for monorepo packages. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 16.3.5 | 4 / 7 | |
| 16.3.4 | 4 / 7 | |
| 16.3.3 | 4 / 7 | |
| 16.3.2 | 4 / 7 | |
| 16.3.1 | 4 / 7 | |
| 16.3.0 | 4 / 7 | |
| 16.2.4 | 4 / 7 | |
| 16.2.3 | 4 / 7 | |
| 16.2.2 | 4 / 7 | |
| 16.2.1 | 4 / 7 | |
| 16.2.0 | 4 / 7 | |
| 16.1.4 | 4 / 7 | |
| 16.1.3 | 4 / 7 | |
| 16.1.2 | 4 / 7 | |
| 16.1.1 | 4 / 7 | |
| 16.1.0 | 4 / 7 | |
| 16.0.8 | 4 / 7 | |
| 16.0.7 | 4 / 7 | |
| 16.0.6 | 4 / 7 | |
| 16.0.5 | 4 / 7 | |
| 16.0.4 | 4 / 7 | |
| 16.0.3 | 4 / 7 | |
| 16.0.2 | 4 / 7 | |
| 16.0.1 | 4 / 7 | |
| 16.0.0 | 4 / 7 | |
| 15.0.11 | 4 / 7 | |
| 15.0.10 | 4 / 7 | |
| 15.0.9 | 4 / 7 | |
| 15.0.8 | 4 / 7 | |
| 15.0.7 | 4 / 7 | |
| 15.0.6 | 4 / 7 | |
| 15.0.5 | 4 / 7 | |
| 15.0.4 | 4 / 7 | |
| 15.0.3 | 4 / 7 | |
| 15.0.2 | 4 / 7 | |
| 15.0.1 | 4 / 7 | |
| 15.0.0 | 4 / 7 | |
| 14.4.1 | 4 / 7 |
v16.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v16.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.