← Home

@contentful/content-source-maps

npm Repository Homepage

Base SDK for building Content Source Maps with Contentful

60
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

it-internalwhydah-gallycontentful-ecosystemmichaelpearce

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:json-pointer AI (phantom-deps): Likely used but not statically detected due to bundled build output. ai
phantom-deps phantom-dep:@vercel/stega AI (phantom-deps): Framework-scoped dep loaded by convention, not direct import. ai

Versions (showing 60 of 60)

Version Deps Published
0.12.2 2 / 3
0.12.1 2 / 3
0.12.0 2 / 3
0.11.44 2 / 3
0.11.43 2 / 3
0.11.42 2 / 3
0.11.41 2 / 3
0.11.40 2 / 3
0.11.39 2 / 3
0.11.38 2 / 3
0.11.37 2 / 3
0.11.36 2 / 3
0.11.35 2 / 3
0.11.34 2 / 3
0.11.33 2 / 3
0.11.32 2 / 3
0.11.31 2 / 3
0.11.30 2 / 3
0.11.29 2 / 3
0.11.28 2 / 3
0.11.27 2 / 3
0.11.26 2 / 3
0.11.25 2 / 3
0.11.24 2 / 3
0.11.23 2 / 3
0.11.22 2 / 3
0.11.21 2 / 3
0.11.20 2 / 3
0.11.19 2 / 3
0.11.18 2 / 3
0.11.17 2 / 3
0.11.16 2 / 3
0.11.15 2 / 3
0.11.14 2 / 3
0.11.13 2 / 3
0.11.12 2 / 3
0.11.10 2 / 2
0.11.9 2 / 2
0.11.8 2 / 2
0.11.7 2 / 2
0.11.6 2 / 2
0.11.5 2 / 2
0.11.4 2 / 2
0.11.3 2 / 2
0.11.2 2 / 2
0.11.1 2 / 2
0.11.0 2 / 2
0.10.0 2 / 2
0.9.0 2 / 2
0.8.0 2 / 2
0.7.0 2 / 2
0.6.1 2 / 2
0.6.0 2 / 2
0.5.0 2 / 2
0.4.2 2 / 2
0.4.1 2 / 2
0.4.0 2 / 2
0.3.0 2 / 2
0.2.0 2 / 1
0.1.0 2 / 1

v0.12.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.12.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.44

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.43

2 findings
MEDIUM Publisher changed: contentful-ecosystem → GitHub Actions (on 2025-11-24, unremoved on npm for 241d) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (contentful-ecosystem) on 2025-11-24. It has since remained available on npm for 241 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.42

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.41

2 findings
MEDIUM Publisher changed: contentful-ecosystem → GitHub Actions (on 2025-11-10, unremoved on npm for 255d) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (contentful-ecosystem) on 2025-11-10. It has since remained available on npm for 255 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.