@peculiar/asn1-android
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): CI/CD migration from manual publish to GitHub Actions explains missing gitHead. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from maintainer account to GitHub Actions CI/CD; SLSA provenance confirms legitimacy. | ai | |
| phantom-deps | phantom-dep:asn1js | AI (phantom-deps): asn1js is a real dependency used transitively via @peculiar/asn1-schema; referenced in config. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 2.8.0 | 3 / 0 | |
| 2.7.0 | 3 / 0 | |
| 2.6.0 | 3 / 0 | |
| 2.5.0 | 3 / 0 | |
| 2.4.0 | 3 / 0 | |
| 2.3.16 | 3 / 0 | |
| 2.3.15 | 3 / 0 | |
| 2.3.13 | 3 / 0 | |
| 2.3.10 | 3 / 0 | |
| 2.3.9 | 3 / 0 | |
| 2.3.8 | 3 / 0 | |
| 2.3.6 | 3 / 0 | |
| 2.3.3 | 3 / 0 | |
| 2.3.0 | 3 / 0 | |
| 2.2.0 | 3 / 0 | |
| 2.1.9 | 3 / 0 | |
| 2.1.8 | 3 / 0 | |
| 2.1.7 | 3 / 0 | |
| 2.1.6 | 3 / 0 | |
| 2.1.5 | 3 / 0 | |
| 2.1.0 | 3 / 0 | |
| 2.0.44 | 3 / 0 | |
| 2.0.38 | 3 / 0 | |
| 2.0.37 | 3 / 0 | |
| 2.0.36 | 3 / 0 | |
| 2.0.32 | 3 / 0 | |
| 2.0.29 | 3 / 0 | |
| 2.0.27 | 3 / 0 | |
| 2.0.26 | 3 / 0 | |
| 2.0.25 | 3 / 0 | |
| 2.0.23 | 3 / 0 | |
| 2.0.17 | 3 / 0 | |
| 2.0.13 | 3 / 0 | |
| 2.0.12 | 3 / 0 | |
| 2.0.11 | 3 / 0 | |
| 2.0.8 | 3 / 0 | |
| 2.0.7 | 3 / 0 |
v2.3.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.