prosemirror-tables
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Build-env change on established package; no malicious behavior. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Legitimate maintainer handoff on canonical package, stable long-term. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size growth is rollup-bundled cjs output plus sourcemap. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 1.8.5 | 5 / 19 | |
| 1.8.4 | 5 / 19 | |
| 1.8.3 | 5 / 19 | |
| 1.8.1 | 5 / 20 | |
| 1.8.0 | 5 / 19 | |
| 1.7.1 | 5 / 19 | |
| 1.7.0 | 5 / 19 | |
| 1.6.4 | 5 / 18 | |
| 1.6.3 | 5 / 18 | |
| 1.6.2 | 5 / 18 | |
| 1.6.1 | 5 / 18 | |
| 1.6.0 | 5 / 18 | |
| 1.5.1 | 5 / 18 | |
| 1.5.0 | 5 / 18 | |
| 1.4.2 | 5 / 18 | |
| 1.4.0 | 5 / 17 | |
| 1.3.7 | 5 / 17 | |
| 1.3.6 | 5 / 17 | |
| 1.3.5 | 5 / 17 | |
| 1.3.4 | 5 / 16 | |
| 1.3.3 | 5 / 16 | |
| 1.3.2 | 5 / 16 | |
| 1.3.1 | 5 / 16 | |
| 1.3.0 | 5 / 17 | |
| 1.2.5 | 5 / 17 | |
| 1.2.4 | 5 / 17 | |
| 1.2.3 | 5 / 18 | |
| 1.2.2 | 5 / 18 | |
| 1.2.1 | 5 / 18 | |
| 1.2.0 | 5 / 18 | |
| 1.1.2 | 5 / 18 | |
| 1.1.1 | 5 / 16 | |
| 1.1.0 | 5 / 16 | |
| 1.0.0 | 5 / 16 |
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.7
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ocavue.
This version was published by a different npm account (ocavue) than the most recent previously approved version (eshvedai) on 2024-02-29. It has since remained available on npm for 871 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ocavue.
This version was published by a different npm account (ocavue) than the most recent previously approved version (eshvedai) on 2024-02-29. It has since remained available on npm for 871 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ocavue.
This version was published by a different npm account (ocavue) than the most recent previously approved version (eshvedai) on 2023-11-28. It has since remained available on npm for 964 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ocavue.
This version was published by a different npm account (ocavue) than the most recent previously approved version (eshvedai) on 2023-06-22. It has since remained available on npm for 1123 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ocavue.
This version was published by a different npm account (ocavue) than the most recent previously approved version (eshvedai) on 2023-06-14. It has since remained available on npm for 1131 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ocavue.
This version was published by a different npm account (ocavue) than the most recent previously approved version (eshvedai) on 2023-01-09. It has since remained available on npm for 1287 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ocavue.
This version was published by a different npm account (ocavue) than the most recent previously approved version (eshvedai) on 2023-01-07. It has since remained available on npm for 1289 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ocavue.
This version was published by a different npm account (ocavue) than the most recent previously approved version (eshvedai) on 2022-12-07. It has since remained available on npm for 1320 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ocavue.
This version was published by a different npm account (ocavue) than the most recent previously approved version (eshvedai) on 2022-08-04. It has since remained available on npm for 1445 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ocavue.
This version was published by a different npm account (ocavue) than the most recent previously approved version (eshvedai) on 2022-07-20. It has since remained available on npm for 1460 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ocavue.
This version was published by a different npm account (ocavue) than the most recent previously approved version (eshvedai) on 2022-07-19. It has since remained available on npm for 1461 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ocavue.
This version was published by a different npm account (ocavue) than the most recent previously approved version (eshvedai) on 2022-07-13. It has since remained available on npm for 1467 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ocavue.
This version was published by a different npm account (ocavue) than the most recent previously approved version (eshvedai) on 2022-07-11. It has since remained available on npm for 1469 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ocavue.
This version was published by a different npm account (ocavue) than the most recent previously approved version (eshvedai) on 2022-07-11. It has since remained available on npm for 1469 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ocavue.
This version was published by a different npm account (ocavue) than the most recent previously approved version (marduke182) on 2022-07-11. It has since remained available on npm for 1469 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (eshvedai) than the most recent previously approved version (marduke182) on 2020-07-31, but eshvedai is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.