@times-components/article-skeleton
The article skeleton
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:mockdate | AI (phantom-deps): mockdate is explicitly listed in both devDependencies and dependencies in package.json; not a true phantom dep. | ai |
Versions (showing 100 of 673)
| Version | Deps | Published |
|---|---|---|
| 1.165.16 | 32 / 26 | |
| 1.165.15 | 32 / 26 | |
| 1.165.14 | 32 / 26 | |
| 1.165.13 | 32 / 26 | |
| 1.165.12 | 32 / 26 | |
| 1.165.11 | 32 / 26 | |
| 1.165.10 | 32 / 26 | |
| 1.165.9 | 32 / 26 | |
| 1.165.8 | 32 / 26 | |
| 1.165.7 | 32 / 26 | |
| 1.165.6 | 32 / 26 | |
| 1.165.5 | 32 / 26 | |
| 1.165.4 | 32 / 26 | |
| 1.165.3 | 32 / 26 | |
| 1.165.2 | 32 / 26 | |
| 1.165.1 | 32 / 26 | |
| 1.165.0 | 32 / 26 | |
| 1.164.1 | 32 / 26 | |
| 1.164.0 | 32 / 26 | |
| 1.163.0 | 32 / 26 | |
| 1.162.3 | 32 / 26 | |
| 1.162.2 | 32 / 26 | |
| 1.162.1 | 32 / 26 | |
| 1.162.0 | 32 / 26 | |
| 1.161.2 | 32 / 26 | |
| 1.161.0 | 32 / 26 | |
| 1.160.2 | 32 / 26 | |
| 1.160.1 | 32 / 26 | |
| 1.160.0 | 32 / 26 | |
| 1.159.0 | 32 / 26 | |
| 1.158.6 | 32 / 26 | |
| 1.158.5 | 32 / 26 | |
| 1.158.4 | 32 / 26 | |
| 1.158.3 | 32 / 26 | |
| 1.158.2 | 32 / 26 | |
| 1.158.1 | 32 / 26 | |
| 1.158.0 | 32 / 26 | |
| 1.157.0 | 32 / 26 | |
| 1.156.0 | 32 / 26 | |
| 1.155.1 | 32 / 26 | |
| 1.155.0 | 32 / 26 | |
| 1.154.0 | 32 / 26 | |
| 1.153.0 | 32 / 26 | |
| 1.152.0 | 32 / 26 | |
| 1.151.1 | 32 / 26 | |
| 1.151.0 | 32 / 26 | |
| 1.150.4 | 32 / 26 | |
| 1.150.3 | 32 / 26 | |
| 1.150.2 | 32 / 26 | |
| 1.150.1 | 32 / 26 | |
| 1.150.0 | 32 / 26 | |
| 1.149.2 | 32 / 26 | |
| 1.149.1 | 32 / 26 | |
| 1.149.0 | 32 / 26 | |
| 1.148.1 | 32 / 26 | |
| 1.148.0 | 32 / 26 | |
| 1.147.2 | 32 / 26 | |
| 1.147.1 | 32 / 26 | |
| 1.147.0 | 32 / 26 | |
| 1.146.0 | 32 / 26 | |
| 1.145.3 | 32 / 26 | |
| 1.145.2 | 32 / 26 | |
| 1.145.1 | 32 / 26 | |
| 1.145.0 | 32 / 26 | |
| 1.144.0 | 32 / 26 | |
| 1.143.0 | 32 / 26 | |
| 1.142.3 | 32 / 26 | |
| 1.142.2 | 32 / 26 | |
| 1.142.1 | 32 / 26 | |
| 1.142.0 | 32 / 26 | |
| 1.141.1 | 32 / 26 | |
| 1.141.0 | 32 / 26 | |
| 1.140.13 | 32 / 26 | |
| 1.140.12 | 32 / 26 | |
| 1.140.11 | 32 / 26 | |
| 1.140.10 | 32 / 26 | |
| 1.140.9 | 32 / 26 | |
| 1.140.8 | 32 / 26 | |
| 1.140.7 | 32 / 26 | |
| 1.140.6 | 32 / 26 | |
| 1.140.5 | 32 / 26 | |
| 1.140.4 | 32 / 26 | |
| 1.140.3 | 32 / 26 | |
| 1.140.2 | 32 / 26 | |
| 1.140.0 | 32 / 26 | |
| 1.139.3 | 32 / 26 | |
| 1.139.1 | 32 / 26 | |
| 1.139.0 | 32 / 26 | |
| 1.138.1 | 32 / 26 | |
| 1.138.0 | 32 / 26 | |
| 1.137.11 | 32 / 26 | |
| 1.137.10 | 32 / 26 | |
| 1.137.9 | 32 / 26 | |
| 1.137.8 | 32 / 26 | |
| 1.137.7 | 32 / 26 | |
| 1.137.6 | 32 / 26 | |
| 1.137.5 | 32 / 26 | |
| 1.137.4 | 32 / 26 | |
| 1.137.3 | 32 / 26 | |
| 1.137.2 | 32 / 26 |
v1.162.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.162.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.162.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.161.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.161.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.160.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.160.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.160.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.159.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.158.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.158.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.158.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.158.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.158.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.158.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.158.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.157.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.156.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.155.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.155.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.154.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.153.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.152.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.151.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.151.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.150.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.150.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.150.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.150.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.150.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.149.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.149.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.149.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.148.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.148.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.147.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.147.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.147.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.146.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.145.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.145.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.145.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.145.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.144.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.143.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.142.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.142.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.142.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.142.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.141.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.141.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.140.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.140.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.140.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.140.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.140.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.140.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.140.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.140.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.140.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.140.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.140.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.140.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.140.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.139.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.139.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.139.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.138.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.138.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.137.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.137.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.137.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.137.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.137.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.137.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.137.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.137.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.137.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.137.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.