@alfresco/js-api
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-published with SLSA attestation; gitHead omission is benign metadata gap. | ai | |
| provenance | publisher-changed | AI (provenance): CI/CD attestation adoption, verified IMPROVED direction, not account compromise. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Swap of one established event-emitter lib for another, not a novel/malicious dep. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IPs are localhost default config values (127.0.0.1) in AlfrescoApiConfig; stable false positive for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 10.0.0 | 2 / 0 | |
| 9.5.0 | 2 / 0 | |
| 9.4.1 | 3 / 0 | |
| 9.4.0 | 3 / 0 | |
| 9.3.1 | 3 / 0 | |
| 9.2.1 | 3 / 0 | |
| 9.2.0 | 3 / 0 | |
| 9.0.2 | 3 / 0 |
v10.0.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[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: GitHub Actions.
v9.3.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-11. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.2
2 findingsThis version was published by a different npm account than previous versions on 2026-02-25. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.