@m4l/styles
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom is declared in dependencies; phantom-dep heuristic fires on config references but dependency is properly declared. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established monorepo package (1145 days, 187 versions); missing repo/keywords typical for internal scoped packages. | ai |
Versions (showing 49 of 49)
| Version | Deps | Published |
|---|---|---|
| 7.1.51 | 1 / 0 | |
| 7.1.50 | 1 / 0 | |
| 7.1.49 | 1 / 0 | |
| 7.1.48 | 1 / 0 | |
| 7.1.47 | 1 / 0 | |
| 7.1.46 | 1 / 0 | |
| 7.1.45 | 1 / 0 | |
| 7.1.44 | 1 / 0 | |
| 7.1.43 | 0 / 0 | |
| 7.1.42 | 0 / 0 | |
| 7.1.41 | 3 / 0 | |
| 7.1.40 | 3 / 0 | |
| 7.1.39 | 3 / 0 | |
| 7.1.37 | 3 / 0 | |
| 7.1.36 | 3 / 0 | |
| 7.1.35 | 3 / 0 | |
| 7.1.34 | 3 / 0 | |
| 7.1.33 | 3 / 0 | |
| 7.1.32 | 3 / 0 | |
| 7.1.31 | 3 / 0 | |
| 7.1.30 | 3 / 0 | |
| 7.1.29 | 3 / 0 | |
| 7.1.28 | 3 / 0 | |
| 7.1.27 | 3 / 0 | |
| 7.1.26 | 3 / 0 | |
| 7.1.25 | 3 / 0 | |
| 7.1.24 | 3 / 0 | |
| 7.1.23 | 3 / 0 | |
| 7.1.22 | 3 / 0 | |
| 7.1.21 | 3 / 0 | |
| 7.1.20 | 3 / 0 | |
| 7.1.19 | 3 / 0 | |
| 7.1.18 | 3 / 0 | |
| 7.1.15 | 3 / 0 | |
| 7.1.14 | 3 / 0 | |
| 7.1.13 | 3 / 0 | |
| 7.1.12 | 3 / 0 | |
| 7.1.11 | 3 / 0 | |
| 7.1.10 | 3 / 0 | |
| 7.1.9 | 3 / 0 | |
| 7.1.8 | 3 / 0 | |
| 7.1.7 | 3 / 0 | |
| 7.1.6 | 3 / 0 | |
| 7.1.5 | 3 / 0 | |
| 7.1.4 | 3 / 0 | |
| 7.1.3 | 3 / 0 | |
| 7.1.2 | 3 / 0 | |
| 7.0.1 | 3 / 0 | |
| 7.0.0 | 3 / 0 |
v7.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.