@absolutejs/isolated-jsc
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established publisher with clean track record; provenance gap is a process issue, not a security signal for this package. | ai | |
| provenance | missing-githead | AI (provenance): Publisher has 42 approved packages and no material changes from prior version; likely a one-off CI environment change. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Publisher has strong track record; rapid publishes consistent with iterative release cadence across 34 versions. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 0.12.4 | 1 / 3 | |
| 0.12.3 | 1 / 3 | |
| 0.12.2 | 1 / 4 | |
| 0.12.1 | 1 / 4 | |
| 0.12.0 | 1 / 4 | |
| 0.11.3 | 1 / 4 | |
| 0.11.2 | 1 / 4 | |
| 0.11.1 | 1 / 4 | |
| 0.11.0 | 1 / 4 | |
| 0.10.0 | 0 / 3 | |
| 0.9.2 | 0 / 3 | |
| 0.9.1 | 0 / 3 | |
| 0.9.0 | 0 / 3 | |
| 0.8.21 | 0 / 3 | |
| 0.8.20 | 0 / 3 | |
| 0.8.19 | 0 / 3 | |
| 0.8.18 | 0 / 3 | |
| 0.8.17 | 0 / 3 | |
| 0.8.16 | 0 / 3 | |
| 0.8.15 | 0 / 3 | |
| 0.8.14 | 0 / 3 | |
| 0.8.13 | 0 / 3 | |
| 0.8.12 | 0 / 3 | |
| 0.8.11 | 0 / 3 | |
| 0.8.10 | 0 / 3 | |
| 0.8.9 | 0 / 3 | |
| 0.8.8 | 0 / 3 | |
| 0.8.7 | 0 / 3 | |
| 0.8.6 | 0 / 3 | |
| 0.8.5 | 0 / 3 | |
| 0.8.4 | 0 / 3 | |
| 0.8.3 | 0 / 3 | |
| 0.8.2 | 0 / 3 | |
| 0.8.1 | 0 / 3 | |
| 0.8.0 | 0 / 3 | |
| 0.7.3 | 0 / 3 | |
| 0.7.2 | 0 / 3 | |
| 0.7.1 | 0 / 3 | |
| 0.7.0 | 0 / 3 | |
| 0.6.0 | 0 / 3 | |
| 0.5.1 | 0 / 3 | |
| 0.5.0 | 0 / 3 | |
| 0.4.0 | 0 / 3 | |
| 0.3.0 | 0 / 3 | |
| 0.2.0 | 0 / 3 | |
| 0.1.0 | 0 / 3 | |
| 0.0.1 | 0 / 3 |
v0.12.4
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: alexkahndev.
v0.12.3
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: alexkahndev.
v0.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.