@pafi-dev/core
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Likely a one-off local publish; no other malicious indicators present in this package. | ai | |
| provenance | no-provenance | AI (provenance): Package consistently published without Sigstore provenance; not a security risk on its own. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped blockchain SDK; name similarity to 'cors' is coincidental, not impersonation. | ai |
Versions (showing 57 of 57)
| Version | Deps | Published |
|---|---|---|
| 0.19.0 | 0 / 6 | |
| 0.18.0 | 0 / 6 | |
| 0.17.0 | 0 / 6 | |
| 0.16.0 | 0 / 6 | |
| 0.15.0 | 0 / 6 | |
| 0.14.0 | 0 / 6 | |
| 0.13.1 | 0 / 6 | |
| 0.13.0 | 0 / 6 | |
| 0.10.0 | 0 / 5 | |
| 0.9.6 | 0 / 5 | |
| 0.9.5 | 0 / 5 | |
| 0.9.4 | 0 / 5 | |
| 0.9.3 | 0 / 5 | |
| 0.9.2 | 0 / 5 | |
| 0.9.1 | 0 / 5 | |
| 0.9.0 | 0 / 5 | |
| 0.8.0 | 0 / 5 | |
| 0.7.10 | 0 / 5 | |
| 0.7.7 | 0 / 5 | |
| 0.7.6 | 0 / 5 | |
| 0.7.5 | 0 / 5 | |
| 0.7.4 | 0 / 5 | |
| 0.7.3 | 0 / 5 | |
| 0.7.2 | 0 / 5 | |
| 0.7.1 | 0 / 5 | |
| 0.7.0 | 0 / 5 | |
| 0.6.2 | 0 / 5 | |
| 0.6.1 | 0 / 5 | |
| 0.6.0 | 0 / 5 | |
| 0.5.22 | 0 / 5 | |
| 0.5.21 | 0 / 5 | |
| 0.5.20 | 0 / 5 | |
| 0.5.19 | 0 / 5 | |
| 0.5.18 | 0 / 5 | |
| 0.5.17 | 0 / 5 | |
| 0.5.16 | 0 / 5 | |
| 0.5.15 | 0 / 5 | |
| 0.5.14 | 0 / 5 | |
| 0.5.13 | 0 / 5 | |
| 0.5.12 | 0 / 5 | |
| 0.5.11 | 0 / 5 | |
| 0.5.10 | 0 / 5 | |
| 0.5.9 | 0 / 5 | |
| 0.5.8 | 0 / 5 | |
| 0.5.7 | 0 / 5 | |
| 0.5.6 | 0 / 5 | |
| 0.5.5 | 0 / 5 | |
| 0.5.4 | 0 / 5 | |
| 0.5.3 | 0 / 5 | |
| 0.5.2 | 0 / 5 | |
| 0.5.1 | 0 / 5 | |
| 0.5.0 | 0 / 5 | |
| 0.4.0 | 0 / 5 | |
| 0.2.0 | 0 / 5 | |
| 0.1.2 | 0 / 5 | |
| 0.1.1 | 0 / 5 | |
| 0.1.0 | 0 / 5 |
v0.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: philliptran.
v0.17.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: philliptran.
v0.16.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: philliptran.
v0.15.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: philliptran.
v0.14.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: philliptran.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: philliptran.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: philliptran.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: philliptran.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: philliptran.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: philliptran.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: philliptran.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: philliptran.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: philliptran.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: philliptran.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: philliptran.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: philliptran.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
2 findingsPackage name '@pafi-dev/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: philliptran.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: philliptran.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.22
2 findingsPackage name '@pafi-dev/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.9
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: philliptran.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: philliptran.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.