@polka-codes/core
[](https://www.npmjs.com/package/@polka-codes/core) [](https://www.npmjs.com/package/@polka-codes/core) [: Transition to GitHub Actions publisher is confirmed legitimate by SLSA provenance attestation from the project's own CI/CD. | ai | |
| phantom-deps | phantom-dep:yaml | AI (phantom-deps): yaml is declared in dependencies and used in config parsing; false positive. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established scoped package with 222 versions and ecosystem adoption; metadata gaps are benign. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped org package @polka-codes/core; name similarity to 'cors' is coincidental, not impersonation. | ai |
Versions (showing 100 of 223)
| Version | Deps | Published |
|---|---|---|
| 0.9.33 | 6 / 0 | |
| 0.9.32 | 6 / 0 | |
| 0.9.31 | 6 / 0 | |
| 0.9.30 | 6 / 0 | |
| 0.9.29 | 6 / 0 | |
| 0.9.28 | 6 / 0 | |
| 0.9.27 | 6 / 0 | |
| 0.9.26 | 6 / 0 | |
| 0.9.25 | 6 / 0 | |
| 0.9.24 | 6 / 0 | |
| 0.9.23 | 6 / 0 | |
| 0.9.22 | 6 / 0 | |
| 0.9.21 | 6 / 0 | |
| 0.9.20 | 6 / 0 | |
| 0.9.19 | 6 / 0 | |
| 0.9.18 | 6 / 0 | |
| 0.9.17 | 6 / 0 | |
| 0.9.16 | 6 / 0 | |
| 0.9.15 | 6 / 0 | |
| 0.9.14 | 6 / 0 | |
| 0.9.13 | 6 / 0 | |
| 0.9.12 | 6 / 0 | |
| 0.9.11 | 6 / 0 | |
| 0.9.10 | 6 / 0 | |
| 0.9.9 | 6 / 0 | |
| 0.9.8 | 6 / 0 | |
| 0.9.7 | 6 / 0 | |
| 0.9.6 | 6 / 0 | |
| 0.9.5 | 6 / 0 | |
| 0.9.4 | 6 / 0 | |
| 0.9.3 | 6 / 0 | |
| 0.9.2 | 6 / 0 | |
| 0.9.1 | 6 / 0 | |
| 0.9.0 | 6 / 0 | |
| 0.8.28 | 5 / 0 | |
| 0.8.27 | 5 / 0 | |
| 0.8.26 | 5 / 0 | |
| 0.8.25 | 5 / 0 | |
| 0.8.24 | 5 / 0 | |
| 0.8.23 | 5 / 0 | |
| 0.8.22 | 5 / 0 | |
| 0.8.21 | 5 / 0 | |
| 0.8.20 | 5 / 0 | |
| 0.8.19 | 5 / 0 | |
| 0.8.18 | 5 / 0 | |
| 0.8.17 | 5 / 0 | |
| 0.8.16 | 5 / 0 | |
| 0.8.15 | 5 / 0 | |
| 0.8.14 | 5 / 0 | |
| 0.8.13 | 5 / 0 | |
| 0.8.12 | 5 / 0 | |
| 0.8.11 | 5 / 0 | |
| 0.8.10 | 5 / 0 | |
| 0.8.9 | 5 / 0 | |
| 0.8.8 | 5 / 0 | |
| 0.8.7 | 5 / 0 | |
| 0.8.6 | 5 / 0 | |
| 0.8.5 | 5 / 0 | |
| 0.8.4 | 5 / 0 | |
| 0.8.3 | 5 / 0 | |
| 0.8.2 | 5 / 0 | |
| 0.8.1 | 4 / 0 | |
| 0.8.0 | 4 / 0 | |
| 0.7.24 | 4 / 0 | |
| 0.7.23 | 4 / 0 | |
| 0.7.22 | 4 / 0 | |
| 0.7.21 | 4 / 0 | |
| 0.7.20 | 4 / 0 | |
| 0.7.19 | 4 / 0 | |
| 0.7.18 | 4 / 0 | |
| 0.7.17 | 4 / 0 | |
| 0.7.16 | 3 / 0 | |
| 0.7.15 | 3 / 0 | |
| 0.7.14 | 3 / 0 | |
| 0.7.13 | 3 / 0 | |
| 0.7.12 | 3 / 0 | |
| 0.7.11 | 3 / 0 | |
| 0.7.10 | 3 / 0 | |
| 0.7.9 | 3 / 0 | |
| 0.7.7 | 3 / 0 | |
| 0.7.6 | 3 / 0 | |
| 0.7.5 | 3 / 0 | |
| 0.7.4 | 3 / 0 | |
| 0.7.3 | 3 / 0 | |
| 0.7.2 | 3 / 0 | |
| 0.7.1 | 3 / 0 | |
| 0.7.0 | 3 / 0 | |
| 0.6.8 | 2 / 0 | |
| 0.6.7 | 2 / 0 | |
| 0.6.6 | 2 / 0 | |
| 0.6.5 | 2 / 0 | |
| 0.6.4 | 2 / 0 | |
| 0.6.3 | 2 / 0 | |
| 0.6.2 | 2 / 0 | |
| 0.6.1 | 2 / 0 | |
| 0.6.0 | 2 / 0 | |
| 0.5.4 | 2 / 0 | |
| 0.5.3 | 2 / 0 | |
| 0.5.2 | 2 / 0 | |
| 0.5.1 | 2 / 0 |
v0.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.